home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Overload Trio 2
/
Shareware Overload Trio Volume 2 (Chestnut CD-ROM).ISO
/
dir24
/
ll232exe.zip
/
LAN-LINK.DOC
< prev
next >
Wrap
Text File
|
1994-06-05
|
454KB
|
10,697 lines
LAN-LINK Version 2.32 PAGE 1
LAN-LINK Copyright (c) 1988 - 1994 by G3ZCZ
All Rights Reserved
Joe Kasser W3/G3ZCZ
POB 3419
Silver Spring
Md., 20918, U.S.A.
Voice (301) 593 6136
Data BBS (301) 593 9067
Internet jkasser@cap.gwu.edu
_______
____|__ | (tm)
--| | |-------------------
| ____|__ | Association of
| | |_| Shareware
|__| o | Professionals
-----| | |---------------------
|___|___| MEMBER
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
LAN-LINK Version 2.32 PAGE 2
Table of Contents
Appendix 1 Introducing LAN-LINK ........................ 2
LAN-LINK PROGRAM HIGHLIGHTS............................ 4
Getting Started ....................................... 7
Bringing LAN-LINK Up the First Time ................... 8
Using the Quick Menu .................................. 9
Connecting to Other Stations .......................... 9
Using Different TNCs .................................. 9
LAN-LINK Memory Requirements ..........................10
PC to TNC Communications ..............................10
LAN-LINK Runs Open Loop ...............................10
In Case of Problems ...................................10
Logbooks ..............................................11
How To Get an Update ..................................11
Starting LAN-LINK in a Non Packet Mode ................11
Using LAN-LINK with a PacketCluster ...................12
Using ANSI Color for Transmitting Text Color Files ....13
Appendix 2 LAN-LINK Features, Menus and Commands ...... 14
1.0 LAN-LINK MESSAGE HANDLING FEATURES ................14
1.1 Answering Machine ..............................14
1.2 Mail Beacon (Annunciator) ......................14
1.3 How to Leave a Message .........................15
2.0 LAN-LINK WINDOWS ..................................15
3.0 HOT KEYS ..........................................19
3.1 Alt-A Alert Call (Packet) & AMTOR ARQ Call/Talk 19
3.2 Alt-B Send Break/AMTOR Changeover ..............19
3.3 Alt-C Call/Connect to Someone ..................19
3.4 Alt-D Disconnect or Receive ....................21
3.5 Alt-E Enter Call ...............................22
3.6 Alt-F Flush TNC Buffer .........................22
3.7 Alt-H Help Information for Function Keys .......22
3.8 Alt-J Jump to DOS ..............................22
3.9 Alt-K PacketCluster DX Alert....................22
3.10 Alt-L Log Contact .............................22
3.11 Alt-M Message Scan ............................22
3.12 Alt-N Next Stream .............................23
3.13 Alt-O Turn Robot On ...........................23
3.14 Alt-P Turn Printer ON/OFF .....................23
3.15 Alt-Q Call QRZ ................................23
3.16 Alt-R Retry Call/Connect ......................23
3.17 Alt-S Scan Log ................................24
3.18 Alt-W :QRA: ...................................24
3.19 Alt-X Exit to DOS .............................24
3.20 Alt-Y Zap PacketCluster/RTTY Transmit "RY"s ...24
3.21 Alt-Z Zap PBBS ................................24
3.22 Alt-= Toggle Miscellaneous Flag ...............26
3.23 End "> +?" [Over] .............................26
3.24 PgUp Scrollback (Scrolls back incoming text) ..27
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
LAN-LINK Version 2.32 PAGE 3
3.25 The Home Key ..................................27
3.26 The Down Arrow Key ............................27
3.27 Shift/Baudrate Control Keys ...................28
3.28 Control-Z (^Z) ................................28
3.29 Control T (^T) ................................28
4.0 FUNCTION KEYS .....................................28
4.1 Capture to Disk Toggle (F1) ....................29
4.2 Send Brag Tape and Talk (F2) ...................29
4.3 Transmit Callsign Sequence (F3) ................29
4.4 Send Brag Tape (F4) ............................30
4.5 Show Packet "MH" list and Point and Shoot
Connect (F5)...............30
4.6 Auto CQ Call (F6) ..............................30
4.7 Activate Type Ahead Buffer/AMTOR Relink (F7) ...31
4.8 Disconnect, Disengage or Receive (F8) ..........32
4.9 Put TNC in CMD Mode (F9) .......................32
4.10 Put TNC in CONVERSE/Transmit/AMTOR FEC (F10) ..32
4.11 Alternate Function Keys .......................33
4.12 Shift Function Keys ...........................33
4.13 Control Function Keys .........................33
5.0 THE MAIN MENU .....................................34
5.1 The Quick Menu .................................34
5.2 Auto CQ ........................................35
5.3 Send Brag Tape .................................35
5.4 Call Someone ...................................35
5.5 Log Menu .......................................35
5.6 Change Communications Mode .....................35
5.7 Call CQ ........................................35
5.8 Send/Talk File .................................35
5.9 QRZ ............................................36
5.10 Send/Talk LAN-LINK Files 001..010 .............36
6.0 THE PBBS/PacketCluster MENU .......................36
6.1 Download Text Files ............................36
6.2 Download Binary File (Xmodem) ..................37
6.3 Download Binary File (Ymodem) ..................37
6.4 Zap PacketCluster ..............................37
6.5 Zap PBBS .......................................37
6.6 Turn PacketCluster Mode ON/OFF .................37
6.7 Send DX Alert ..................................38
6.8 Clear All Search Flags .........................38
6.9 Set All Search Flags ...........................38
6.10 Set All CW Search Flags .......................38
6.11 Set All SSB Search Flags ......................38
6.12 Set/Clear Individual Search Flags .............38
6.13 Set/Clear Current Band Search Flags ...........38
7.0 THE CALL MENU .....................................39
7.1 Alert Call .....................................39
7.2 ReMember Path ..................................40
7.3 Call CQ ........................................40
7.4 Show Contents of Call Directory ................40
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
LAN-LINK Version 2.32 PAGE 4
7.5 Target Call ....................................40
7.6 Auto CQ ........................................41
7.7 Toggle DX Flag .................................41
7.8 Zap PBBS on Next Mail Beacon ...................41
8.0 EDIT MENU .........................................41
8.1 Edit Brag Tape .................................43
8.2 Edit Call Directory File .......................44
8.3 Edit Any Other File ............................44
8.4 Answer Capture-to-disk (Ctdsk) File
(Split Screen) ...........44
8.5 Answer Incoming Messages (Split Screen) ........44
8.6 Leave Note for Someone .........................44
8.7 Edit Capture-to-Disk file ......................45
8.8 Edit Two Files (Split Screen) ..................45
8.9 Edit Configuration File ........................45
8.10 Edit LAN-LINK.001 through LAN-LINK.010 Files ..45
8.11 Pick Capture-to-disk File to Edit .............45
8.12 Pick Message File to Edit .....................45
8.13 Leave Messages on your local PBBS .............46
8.14 Edit Incoming Message .........................46
8.15 Edit LAN-LINK.OUT File ........................46
8.16 Edit LAN-LINK.DMO File ........................46
8.17 Pick dEmo File to Edit ........................46
9.0 EVENT/CLOCK MENU ..................................46
9.1 Set Alarm ......................................47
9.2 Connect ........................................47
9.3 Display Event ..................................47
9.4 Periodic Event .................................47
9.5 Turn Robot ON/OFF ..............................47
9.6 Turn Contest ON/OFF ............................47
9.7 Turn Time Display ON/OFF .......................47
9.8 Cancel Event ...................................47
9.9 Zap PBBS .......................................47
10.0 FILES MENU .......................................48
10.1 Send Brag Tape ................................48
10.2 File Directory ................................49
10.3 Erase File ....................................49
10.4 Pick Capture-to-disk (Ctdsk) file to View .....49
10.5 Rename File ...................................49
10.6 Send File .....................................49
10.7 Send/Talk File ................................49
10.8 Send Uppercase File ...........................49
10.9 View File .....................................49
10.10 View Capture-to-disk (Ctdsk) File ............50
10.11 View Incoming Message File ...................50
10.12 Print File ...................................50
10.13 View Color File ..............................50
10.14 Turn Mode Files ON/OFF .......................50
10.15 Turn eXpand Files ON/OFF .....................50
11.0 HELP WITH FUNCTION KEYS ..........................50
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
LAN-LINK Version 2.32 PAGE 5
12.0 JUMP TO DOS SHELL ................................51
13.0 LAN-LINK MENU ....................................51
13.1 :QBU: External Protocol Command ...............51
13.2 :QBM: ASCII File ..............................52
13.3 :QDB: ASCII File ..............................52
13.4 :QIC: Page Operator ...........................52
13.5 :QMH: Monitor Heard ...........................53
13.6 :QRA: Who is "ON-LINE" ........................53
13.7 :QRU: Messages ................................53
13.8 :QSM: Message .................................53
13.9 :QSP: Message .................................54
13.10 :QTA: Messages ...............................54
13.11 :QTR: Ask for Time ...........................54
13.12 :QZD: Binary Files ...........................54
13.13 :QZU: Binary Files ...........................55
13.14 Demo Mode ....................................55
13.5 Set Single/Dual PK-900/DSP 2232 In Windows.....55
14.0 LOG MENU .........................................55
14.1 Append From Another LAN-LINK Log ..............56
14.2 Scan Log by Band ..............................56
14.3 Change Logbook File ...........................56
14.4 Delete Logbook File ...........................57
14.5 Find Date .....................................57
14.6 Purge Log .....................................57
14.7 Help Function Keys ............................57
14.8 Import From G3ZCZ's Contest Log ...............57
14.9 Jump to an Entry ..............................58
14.10 Pick a Log file ..............................58
14.11 Pack a Logbook ...............................58
14.12 Scan Log by Mode .............................58
14.13 Create a New Logbook .........................58
14.14 Print Log ....................................58
14.15 Re-index a Logbook ...........................58
14.16 Sort on Date + Time ..........................58
14.17 Turn Update Disk ON/OFF ......................59
14.18 Fuzzy Scan ...................................59
14.19 Turn Secondary Search ON/OFF .................59
14.20 Log Menu Function Keys .......................59
15.0 MESSAGE MENU .....................................61
15.1 PBBS Command Files ............................62
15.2 Current Messages ..............................62
15.3 View Message ..................................62
15.4 Leave Note ....................................62
15.5 Old Messages ..................................62
15.6 Time Tag ......................................62
16.0 TNC MENU .........................................63
16.1 Set TNC Date/Time .............................64
16.2 Flush TNC Buffer ..............................64
16.3 Initialize TNC ................................64
16.4 Show Calls Monitored List .....................65
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
LAN-LINK Version 2.32 PAGE 6
16.5 Show Connect Status ...........................65
16.6 Change CTEXT ..................................65
16.7 Activate TNC Mailbox ..........................65
16.8 Deactivate TNC Mailbox ........................66
16.9 TNC Modem Menu.................................66
16.10 Select Radio Port 1...........................66
16.11 Select Radio Port 2...........................66
16.12 Disable Radio Port 1..........................66
16.13 Disable Radio Port 2..........................66
16.14 Enable Radio Port 1...........................66
16.16 Enable Radio Port 2...........................66
16.17 Show ### Radio Port...........................66
17.0 AMSAT-OSCAR MENU .................................67
17.1 Full Duplex ON/OFF.............................67
17.2 SAREX MENU ....................................67
17.2.6 Set Attack Mode to Connect/CQ ...............69
17.3 SAREX Orbiter Features ........................69
18.0 PARAMETER MENU ...................................72
18.1 Turn Beacon Mode ON/OFF .......................72
18.2 Clear Connect Counter .........................73
18.3 TNC Custom Line (TNC Parameter) ...............74
18.4 Turn Beacon Control ON/OFF ....................76
18.5 Turn Command Echo ON/OFF ......................76
18.6 Change Keyboard Beep Count ....................76
18.7 Set Message Count .............................77
18.8 Turn Node Drop Link ON/OFF ....................77
18.9 Turn Printer ON/OFF ...........................77
18.10 Turn QTC Snatch ON/OFF .......................77
18.11 Turn :QSP: Relay Flag ON/OFF .................78
18.12 Turn Sound ON/OFF ............................79
18.13 Turn Contest Mode ON/OFF .....................79
18.14 Turn DCD Flag ON/OFF .........................80
18.15 Turn PBBS Snatch ON/OFF ......................80
18.16 Turn Time Id. ON/OFF .........................81
18.17 Turn Automatic Capture-to-Disk Flag ON/OFF ...81
18.18 Change PBBS Parameters .......................81
18.19 Change Callsigns .............................82
18.20 Change Directories ...........................83
18.21 Enter Common Calls ...........................84
18.22 Change File Names ............................84
18.23 Change LAN-LINK Parameters ...................84
18.24 Change PC Communications Parameters ..........88
18.25 Change Colors ................................89
18.26 Change SAREX Parameters ......................92
18.27 Update Configuration File ....................93
18.28 Verify Changes ...............................93
18.29 Change Scan Words ............................93
18.30 Turn Miscellaneous Flag ON/OFF ...............93
18.31 Change Band/Mode .............................95
18.32 Zap PBBS on Next Mail Beacon .................95
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
LAN-LINK Version 2.32 PAGE 7
18.33 PBBS Zap, Don't Disconnect After Sequence ....95
18.34 Control Send of LAN-LINK.OUT .................95
19.0 Q Codes [NC/L] ...................................95
20.0 COMMUNICATIONS MODES .............................96
20.1 VHF PACKET ....................................96
20.2 HF PACKET .....................................96
20.3 ASCII (RTTY) ..................................96
20.4 BAUDOT (RTTY) .................................96
20.5 MORSE (CW) ....................................97
20.6 AMTOR (STANDBY) ...............................97
20.7 AMTOR (MONITOR) ...............................97
20.8 PACTOR (STANDBY) ..............................97
20.9 PACTOR (MONITOR) ..............................97
20.10 SIGNAL .......................................98
20.11 NAVTEX .......................................98
20.12 G-TOR .......................................98
20.13 MANUAL .......................................98
21.0 TERMINAL MODE MENU ...............................98
21.1 Packet Terminal Menu ..........................98
21.2 AMTOR Terminal Menu ..........................103
21.3 Baudot Terminal Menu .........................104
21.4 ASCII Terminal Menu ..........................106
21.5 CW Menu ......................................107
21.6 Pactor Terminal Menu .........................108
22.0 EXIT TO DOS .....................................109
23.0 THE ELMER MENU ..................................109
23.1 Change ELMER File ............................109
23.2 Turn ELMER ON/OFF ............................109
23.3 Load State Table (ELMER.QSO) .................109
23.4 Pick File to Edit ............................110
23.5 Edit State Table (ELMER.QSO) .................110
23.6 Show State Table .............................110
24.0 RADIO MENU ......................................110
24.1 Select VFO A/B................................110
24.2 Set Mode......................................111
24.3 Turn Flag QSY ON/OFF or N/A ..................111
24.4 Read VFO Frequency............................111
24.5 Set VFO Frequency.............................111
24.1 24.6 Speak Frequency..........................111
Appendix 3 LAN-LINK Disk Files ........................112
1.0 LAN-LINK.EXE .....................................112
2.0 LAN-LINK.SYS .....................................112
2.1 CTEXT Line ....................................115
2.2 ELMER Flag ....................................115
2.3 PC Port 4 Custom Address ......................115
2.4 PC Port 4 Custom IRQ ..........................115
2.5 VHF Stream Switch Character ...................115
2.6 HF Stream Switch Character ....................116
2.7 TNC Error Message .............................116
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
LAN-LINK Version 2.32 PAGE 8
2.8 Connect Timeout Delay .........................116
2.9 ELMER Configuration File ......................116
2.10 Expand Transmitted Files Flag ................116
2.11 First PacketCluster Command ..................116
2.12 Second PacketCluster Command .................116
2.13 TNC Mailbox ON Command .......................116
2.14 TNC Mailbox OFF Command ......................117
2.15 VHF Maxframe Command .........................117
2.16 HF Maxframe Command ..........................117
2.17 Inhibit VHF Logging Flag .....................117
2.18 Inhibit HF Logging Flag ......................117
2.19 Printer Permanent Flag .......................117
2.20 Log Disk Update Flag .........................117
2.21 Secondary Log Flag ...........................117
2.22 Auto Answer Flag .............................117
2.23 Ctdsk File Disk Update Flag ..................118
2.24 Default CW Speed .............................118
2.25 Secondary Logbook ............................118
2.26 BBS List Command .............................118
2.27 BBS List Mine Command ........................118
2.28 BBS Custom Command ...........................118
2.29 BBS Bye Command ..............................118
2.30 Start Up Packet Terminal Mode ................118
2.31 Page Time (:QIC: Seconds) ....................119
2.32 PacketCluster DX Alert Tone CW Dit time ......119
2.33 Packet Cluster DX Alert Tone CW Note .........119
2.34 Mode File Flag ...............................119
2.35 BAUDOT Color Change Text String ..............119
2.36 Dual Window Flag .............................119
2.37 TNC String for Modem 9600 baud ...............119
2.38 TNC String for Modem 1200 baud ...............119
2.39 TNC String for Modem RTTY ....................120
2.40 TNC String for Modem 300 baud ................120
2.41 TNC String for Modem RTTY and 1200 baud ......120
2.42 TNC String for Modem 300 baud and 1200 baud ..120
2.43 TNC String for Modem Fuji ....................120
2.44 Delay after a command line ...................120
2.45 Radio ........................................120
2.46 Radio Port ...................................120
2.47 Radio Port baud rate .........................120
2.48 Radio Port Bits ..............................121
2.49 Radio Port Stopbits ..........................121
2.50 Radio Port Parity ............................121
2.51 Radio Address ................................121
2.52 Flag QSY .....................................121
2.53 Flag DX Alert Prefix Check ...................121
2.54 Band parameters for DX Alert message
Log search ...............121
2.55 Modes for DX Alert message log search ........122
2.56 TNC Parameters ...............................122
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
LAN-LINK Version 2.32 PAGE 9
3.0 *.RUN ............................................122
4.0 *.DBF (HF.DBF and VHF.DBF) .......................122
5.0 LAN-LINK.DIR .....................................122
6.0 CONFIG.SYS .......................................123
7.0 *.MBX ............................................123
8.0 *.BBS ............................................124
9.0 LAN-LINK.001 - LAN-LINK.010 ......................125
10.0 QBU-RX.BAT ......................................126
11.0 QBU-TX.BAT ......................................126
12.0 LAN-LINK.QTA ....................................126
13.0 QZ*.BAT .........................................126
14.0 ELMER.QSO .......................................127
15.0 LAN-LINK.OUT ....................................127
16.0 *.DMO ...........................................127
Appendix 4 Local Area Network Capability ..............128
1.0 LAN Protocol (G3ZCZ Version) .....................128
2.0 Message Format ...................................129
3.0 ASCII File Uploading/Downloading .................129
4.0 Path Determination to a DX station ...............130
5.0 Binary File Transfers ............................131
6.0 Requirements for Transfer Protocols ..............131
7.0 The Zmodem Protocol ..............................132
8.0 The PCZ Zmodem Package ...........................132
9.0 BASIC NC/L DICTIONARY ............................133
9.1 :QBM: .........................................133
9.2 :QDB: .........................................134
9.3 :QMH: .........................................134
9.4 :QSM: .........................................134
9.5 :QSP: .........................................134
9.6 :QRA: .........................................134
9.7 :QRT: .........................................134
9.8 :QRU: .........................................134
9.9 :QNO: .........................................135
9.10 :QJG: ........................................135
9.11 :QRV: ........................................135
9.12 :QSL: ........................................135
9.13 :QTA: message ................................135
9.14 :QTC: Message List ...........................135
9.15 :QBU: External Protocols .....................136
9.16 :QZU: Zmodem Binary File Upload ..............136
9.17 :QZD: Zmodem Binary File download ............136
9.18 :QIC: Page Operator ..........................136
9.19 :QTR: Ask for Time ...........................136
Appendix 5 Using Different TNCs .......................137
1.0 TNC2 (MFJ 1270) ..................................137
2.0 TNC1 (HK-4040) ...................................137
3.0 Kantronics KPC-2 .................................137
4.0 Kantronics KAM ...................................138
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
LAN-LINK Version 2.32 PAGE 10
5.0 PK-232 ...........................................138
6.0 MFJ 1278 .........................................138
7.0 Heath HK-21 ......................................139
8.0 PK-900 and DSP 2232 ..............................139
Appendix 6 Anomalies and Bugs .........................140
1.0 Command/Converse Mode Anomalies ..................140
2.0 Buffer Messages in AMTOR Beacon CQ Mode ..........140
3.0 FEC +? Responses in AMTOR Beacon CQ Mode .........140
4.0 Using a Monochrome Monitor .......................140
5.0 The Packet Conference Mode .......................140
6.0 Packet Conference Mode Disconnects ...............141
7.0 Strange Events ...................................141
8.0 *** DISCONNECTED .................................141
9.0 *** CONNECTED ....................................141
10.0 Greek Characters and Other Garbage in the
Incoming Screen ..........142
11.0 Dumb TNC ........................................142
12.0 Intermittent Lockup .............................142
13.0 Automatic Functions Don't Work ..................142
14.0 BBS Zap Failure .................................142
15.0 LAN-LINK Forgets the Band/Power Information .....143
16.0 Zmodem Binary Transfer Problems .................143
Appendix 7 Updates, Revision History ..................144
Appendix 8 ELMER An Expert System Based on a Finite
State Machine ............145
1.0 INTRODUCTION .....................................145
1.1 Expert Systems ................................146
1.2 The User Interface ............................146
1.3 The Knowledge Base ............................146
1.4 The Inference Engine ..........................146
1.5 Features of an Expert System ..................146
1.6 Using an Expert System ........................147
1.7 The Semantic Network ..........................147
1.8 A State Machine ...............................148
1.9 The User Perception ...........................148
1.10 ELMER ........................................148
1.11 Responses to an Input ........................148
1.12 Syntactic Analysis ...........................149
1.13 Programming ELMER ............................149
2.0 The State Table (ELMER.QSO) File .................150
2.1 The Directory Path to the ELMER Text Files ....150
2.2 The Start Up File .............................150
2.3 Window Colors .................................150
2.4 The ELMER Initial State .......................151
2.5 State Machine Parameters ......................151
2.6 The State Machine File ........................152
2.7 Example of Programming the State Table ........152
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
LAN-LINK Version 2.32 PAGE 11
3.0 The Stand Alone Version Status Window ............153
4.0 The Stand Alone Menu .............................153
4.1 Edit Any File .................................153
4.2 Load State Table (ELMER.QSO) ..................153
4.3 Pick File to Edit .............................154
4.4 Edit State Table (ELMER.QSO) ..................154
4.5 eXit to DOS ...................................154
4.6 Show State Table ..............................154
Appendix 9 PCZ Binary file Transfers ..................155
Appendix 10 Other Products by Joe Kasser, W3/G3ZCZ.....168
1.0 PC-HAM 3.52 ......................................168
2.0 STARTREK The Computer Program ....................168
3.0 WHATS-UP 1.30 ....................................169
4.0 ELMER 1.00 .......................................170
5.0 BASIC PACKET RADIO ...............................170
Appendix 11 How shareware Works .......................172
Appendix 12 LAN-LINK 2.32 REGISTRATION FORM ...........174
INDEX .................................................175
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 2
Appendix 1 Introducing LAN-LINK
LAN-LINK is distributed as a Shareware product. You may freely
copy and share the product for non commercial use, with your
friends, associates and other radio amateurs. If you decide to
use the product, become a registered user by completing the
registration form in Appendix 12, and sending it (or a copy), and
$45.00 or equivalent in foreign currency to the author
(Mastercard and Visa accepted). All checks should be drawn on US
banks. Canadians, please use postal money order. Upon receipt of
your registration, you will receive one free update disk,
telephone and mail (electronic and regular) support. If you are
not satisfied with the program after registering it, your money
will be refunded no questions asked, for up to 30 days from the
date your registration was acknowledged.
European Radio Amateur users may register (30.00 Pounds Sterling,
includes V.A.T.) and obtain support from Terry Dansey at
ReadyCrest Ltd., PO Box 75, Chatham, Kent, ME5 9DL, England.
ReadyCrest Ltd. accepts credit cards (Access, Visa, MasterCard
and Eurocard). Telephones: Voice 44 (0) 634-687168, FAX 44
(0)634- 687178, Data (BBS) 44 (0)634-200931.
LAN-LINK may not be sold or distributed with another product
without the express written permission of Joe Kasser, G3ZCZ. Joe
Kasser, G3ZCZ will only support unmodified copies of this
software.
Potential Commercial Users please contact Joe Kasser directly for
modifications and/or details of Site licensing.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 3
LAN-LINK is a Personal Packet Terminal Program for the TNC1,
TNC2, KPC-2, and, most of all, a smart multi-mode digital
communications controller for the KAM, MFJ1278, DSP-2232, PK-900
and the PK-232. LAN-LINK is designed to optimize the configura-
tion of the TNC in each communications mode and to provide some
smart terminal features. It is designed to allow anyone to use
and get the most out of their packet TNC as well as from the PK-
232, the MFJ1278, and the KAM for Morse, ASCII, BAUDOT, AMTOR,
Pactor as well as Packet Radio communications without having to
keep the manual handy.
LAN-LINK is a sophisticated program. In its basic state it allows
you to use the TNC in an optimal manner. It configures the TNC
(it types the commands) for you to maximize the communications
efficiency in the communications mode of your choice. That means,
for example, when working Packet on HF you need to program the
TNC parameters to different values than you would use on VHF to
make maximum use of the mode. One significant difference is the
length of the packet itself, for the longer it is, the greater
the probability of QRM destroying it. This program will adjust
the packet parameters for you.
Since the computer is now involved, other features have been
added to simplify operation, and several features have been
automated. All these operations are performed using menus and
function keys as documented below. It will take a while to learn
how to use this program in a manner which suits you. Read this
document and have fun. After all, isn't that one of the purposes
of Amateur Radio.
The LAN-LINK manual is organized by menu. It describes the
operation of each menu option and function key in each
Communications Mode. The manual tells you what LAN-LINK can do.
It does not tell you how to use LAN-LINK.
Any Terminal Node Controller (TNC) is a complex piece of
equipment. It can operate in a Command Mode, in which you tell it
to do something, or in a Converse Mode in which you are using it
to talk to other stations. Many people confuse the two when first
getting on Packet. If you monitor the channels you will recognize
Command Mode TNC instructions on the air, and when you use the
TNC you will receive the "error" reply when you type something
thinking you are in the Converse Mode but are really in the Com-
mand Mode. LAN-LINK is designed to make Packet operation simple
using Menus and high level (Function and Hot key combinations)
commands.
Morse, ASCII, BAUDOT communications modes are HALF DUPLEX. One
station is transmitting at any time. You thus have to use the
Transmit-Converse and Receive-Disconnect function keys to turn
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 4
the transmitter on and off respectively.
AMTOR is also HALF DUPLEX but has some of the attributes of full
duplex. In this Mode you control who is talking through software.
Only one station can send data at a time, but you can type
characters in to the buffer and they will be transmitted
automatically when the other station turns the QSO over to you.
Once you have linked with someone, you do not use the
Receive/Disconnect function until the QSO is over.
Both stations are communicating automatically thanks to the TNC.
If you want the other operator to respond type the "+?" key
sequence (or use the "End" Key).
Packet Radio communications on the other hand is a full duplex
mode of communications. Once you have connected with someone, you
do not use the Receive-Disconnect function until the QSO is over.
Both stations are communicating automatically thanks to the TNC.
If you want the other operator to respond type the ">" key
followed by the "Enter" Key. Better yet, use the "End" Key.
Morse, AMTOR, ASCII and BAUDOT are character mode communications
in that each character you type is sent as you type them. In
Packet Communications, the TNC stores them up and sends out a
burst or packet when you type the "Enter" Key or you type enough
characters to fill up a packet. Studies have shown that the human
attention span when sitting at the keyboard is of the order of 2
seconds. If you are in a keyboard to keyboard packet radio
connect, remember this and don't forget to use the "Enter" Key
frequently, especially before you stop to think about what to
send next.
AMTOR, Pactor, and PACKET are full duplex modes of communica-
tions. When you connect with someone, there is no need to use the
transmit and receive function keys. In fact you will have
problems if you do. Do not disconnect or break the link until the
QSO is over.
LAN-LINK PROGRAM HIGHLIGHTS
* First packet radio software to be flown in Space.
* Function key and Menu driven.
* Smart PacketCluster features, i.e. automatic QSY to the
frequency of a DX Alert (if in PacketCluster mode).
* Automatic search of HF logbook in response to a Packet-
Cluster DX Alert Message. Customizable levels of
notification. Audio Notification of Prefix status.
* Start Up Communications mode is customizable.
* Start Up Packet terminal mode is customizable.
* Allows you to search through 2 logbooks for previous
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 5
contacts.
* 60 Different Bragtapes/files, 10 in each communications
mode.
* Automatic logbook entries for Pactor, Packet and Mailbox
Beacon Mode AMTOR Connects, semiautomatic logbook entries
for other modes.
* Provides artificial intelligence in the shape of a second
operator (ELMER).
* Logbook file is dBASE compatible and can be processed by the
LOGBOOK Package of PC-HAM by G3ZCZ for indexed listings,
tracking of DXCC and other AWARDS, etc.
* Contest operation, sends standard message and automatically
increments QSO count.
* Automatic optimized configuration of the TNC for each commu-
nications mode.
* All mode Function key "OVER" feature (End key).
* There are 10 files with fixed names (LAN-LINK.001 through
LAN-LINK.010) which may be viewed and transmitted by means
of function keys. They may also be edited from the Edit
Menu.
* Set up of TNC for AMSAT-OSCAR Telemetry reception.
* Time display and event scheduler.
* ASCII Text Editor.
* Customizable Colors.
* Access to the TNC Command Mode is provided in case the user
wishes to override any defaults.
In Packet Radio
* LAN message store and forward capability.
* Automatic capture to disk of all packet radio connects.
* Automatic indication of the number of Packet connects.
* Capable of automatic connect attempts to download a QTC from
another station in the LAN.
* Capable of automatic connect attempts to a packet BBS to
download your incoming messages, when your callsign appears
on the BBS mail beacon annunciator.
* Capable of automatically requesting Bulletins on subjects
that interest you from your local PBBS.
* Digipeat monitoring and capture.
* Alert signal to let you know when a predetermined call shows
up in a packet header on frequency.
* Conference and Bridge modes in multi-connect situations.
* Path determination to DX station via :QMH:.
* Indicator that a specific station designated as the "target"
call connected in Packet Mode, or linked to AMTOR Beacon or
Mailbox while you were away.
* Automatic NET/ROM and KA-Node path set up from directory
file.
* Selective answering machine and MAILBOX using NC/L command
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 6
dialogue.
* Screen indication of connect by desired station (target
call).
* Automatic Beacon Mode CQ caller.
* Automatic contest (DX-pedition) mode.
* Will call CQ repetitively and either work the connect and
keep going after disconnect or signal you when a reply is
received.
* Zmodem binary file transfer capability
* Customizable BBS Zap Commands.
* CTEXT File (LAN-LINK.OUT) which can be sent to all incoming
connects.
* ANSI Colors for Color "Brag Tapes".
* SAREX Attack mode lets you digipeat/CQ via the SAREX station
as well as try a connect. Use the CQ feature to digipeat via
MIR, and the connect for the Space Shuttle.
* Trigger to determine who else is on channel.
* Single keystroke Packet Cluster connect.
In Pactor
* Smart Answering Machine.
* CTEXT File (LAN-LINK.OUT) which can be sent to all incoming
connects.
* ANSI Colors for Color "Brag Tapes".
* Automatic logging of connects.
In AMTOR
* Automatic SELCAL determination.
* Automatic CQ caller. Will call CQ repetitively and signal
you when a reply is received.
* LAN message store and forward capability.
* Selective answering machine and MAILBOX using NC/L command
dialogue.
* Function key change from monitoring FEC CQs to QSOs in
progress (chirpcopy).
* Automatic Beacon Mode CQ caller.
* Automatic contest (DX-pedition) mode.
* Color changes between incoming and outgoing (echoed as sent)
text.
In MORSE/BAUDOT/ASCII
* Automatic CQ caller. Will call CQ repetitively and signal
you when a reply is received.
* RTTY SELCAL.
* NAVY MARS RTTY file transmitting protocols.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 7
Getting Started
MAKE A BACK UP COPY OF THE DISK, BEFORE YOU REMOVE THE WRITE
PROTECT TAB. If you are upgrading from a previous version of LAN-
LINK, the 2.32 configuration files are NOT compatible with
earlier ones. If you are running 2.00, 2.10, 2.20, or 2.20B use the
UPGRADE program to save your current settings. If you have a
previous version, you have to go through the install sequence.
Place the floppy disk in Drive A: Type "A:" (without the "")
followed by the "Enter" key so that you see the A:> prompt. The
floppy disk contains a batch file which will set up the correct
subdirectories on your hard disk. Type "SETUPLL", touch the
"Enter" key, and the batch file will go to work.
The Install program customizes the most often used parameters for
you. Section 18 of Appendix 2 describes each of the parameters.
Read it as you install LAN-LINK.
Install first asks you for the TNC you are using, reply with the
number associated with your TNC. If you don't find your TNC
listed, try the TNC2 option.
The main things you need to change are:
Your Callsign
Your SELCAL (if you are using a Multi-mode TNC).
PacketCluster Call the callsign of your local PacketCluster.
BBS Call the callsign of your local BBS.
If you have not already connected to your local BBS, skip the
next few parameters, and re-run install at some later time when
you know which answers to reply with, or change them from the
LAN-LINK Parameter menu. These parameters are:
BBS Mail Trigger text in your local PBBS mail beacon.
Read Request the command you send to the PBBS to read a
message.
Bulletin Read the command you send to the PBBS to read a
bulletin).
BBS Subject the PBBS prompt for the subject of a
message you are sending.
BBS Message the PBBS prompt for the text of a message
you are sending.
The next few parameters set up the serial port between the PC and
the TNC. Read the TNC Manual to see what the manufacturer's
defaults are. These parameters are:-
PC Com Port A 0 disables serial I/O. Set to the Port
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 8
number you wish to use.
PC Baud Rate Enter the value you want to use.
Data Bits 7 or 8. Note: 7 will inhibit binary trans-
fers.
Parity Bit Enter the correct letter.
Stop bits Use 1 unless the baud rate is 300 or less.
Read Section 18 of Appendix 2 to learn what the remaining
parameters mean. You can change most of them, once you have
loaded LAN-LINK, by bringing up the Parameters Menu, and
following the prompts.
Bringing LAN-LINK Up the First Time
1 If you are upgrading from 2.00, 2.10 or 2.20, use the
UPGRADE program. Any other earlier version, or if this is
your first time, run the INSTALL program.
2 Turn on the TNC.
3 Load the program by typing LAN-LINK in the way you normally
load a program.
4 WAIT until the program says it has initialized the TNC and
shows the band and power in the status window at the top of
the screen.
5 If there is no battery in your TNC do what the TNC manual
tells you to do to synchronize the TERMINAL baud rate to
1200 baud.
6 After LAN-LINK has loaded, use the Parameters Menu to change
anything you still need to customize. Use the "U" option to
save the updated file. After reading the rest of this
manual, you may want to change other defaults to set up LAN-
LINK the way you like it.
7 Use the "N" and "I" options in the TNC Menu to configure the
TNC. Then select the desired mode of operation from the
displayed menu by pressing the appropriate key.
8 Exit from LAN-LINK by using the Alt-X Key or the Esc Key
followed by the X Key.
9 Reload LAN-LINK the same way you did before. This will load
the edited LAN-LINK.SYS file with the new settings. You are
now ready to use LAN-LINK. If this is your first time, try
the Quick Menu.
10 If you are updating from previous versions the following
applies. The LAN-LINK.SYS configuration files are incompat-
ible with any earlier version.
If you have batteries in the TNC, make sure the TNC is set for a
terminal baud rate of 1200, and try to run the program. If you
see Greek characters or it doesn't work, remove the batteries and
try again. You can then replace the batteries and from then on
the program will be correct. Make sure you leave the TNC on when
you replace the batteries or your initialization will revert to
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 9
the TNC default settings - the batteries are there to power the
TNC RAM while your primary power is off.
If you have trouble with a PK232MBX, then, with LAN-LINK running,
turn the PK232MBX off, count to ten and turn it on again. Type
one * character. If that fails, repeat this a few times. If it
still fails, open the PK232 and remove the battery jumper. Count
to 10 slowly before replacing it and try again.
Using the Quick Menu
The Quick Menu is designed for new users and provides the most
commonly used functions in a single Menu. You bring up the Quick
Menu by touching the "Escape" key to access the Main Menu and
then selecting the "A" option.
The Quick Menu is described in Section 5.1 of Appendix 2.
Connecting to Other Stations
LAN-LINK treats incoming connects and outgoing connects
differently. To connect to another station, Use the Alt-C hot
key, Function key 5, or bring up the Quick Menu using the "Esc A"
character sequence as described in Section 5.1, or by bringing up
the Call Menu via the "Esc C" character sequence. DO NOT TYPE "C
Call sign" in the command mode. If you do, the connect will still
take place (the TNC won't know if you or LAN-LINK issued the
command) but LAN-LINK will treat it as an incoming connect and
issue the "[ZCZ] LAN-LINK 2.32>" handshaking signal (if the LAN-
LINK flag is in its default, or enabled state). If you connect to
a PBBS or a Node this way, you will get an error message back
from the PBBS or node, since it does not recognize LAN-LINK's
handshake.
When you use the menu, Alt-C or F5 approach you can also make use
of the "path memory" feature in the LAN-LINK.DIR file.
Using Different TNCs
There are differences between the command dialogue and the
features offered by the PK-232, PK-900, DSP 2232, TNC2 KAM, and
MFJ1278. LAN-LINK makes use of many of them. For example, the KAM
shows the HF and VHF packets as if they were separate streams.
LAN-LINK detects them and displays the different headers in
different colors. As this feature is not present in the PK-232,
LAN-LINK does not offer it for PK-232 users. From time to time,
as each manufacturer updates the firmware (EPROM) in the TNC,
LAN-LINK may be updated and new features added.
LAN-LINK is normally loaded by typing LAN-LINK followed by the
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 10
"Enter" key. In this instance, LAN-LINK gets its configuration
information from the LAN-LINK.SYS file. LAN-LINK.SYS is the
default SYSTEM or configuration file. If you have more than one
TNC you may want to set up different configuration files for each
TNC.
To load LAN-LINK with the optional configuration file, type "LAN-
LINK" followed by the name of the file (without the filetype) on
the command line then press the "Enter" Key. For example, if you
have a PK-232 and a TNC2 and occasionally use the TNC2, set up
the LAN-LINK.SYS file for the PK-232. Then type "LAN-LINK" to run
the program normally. On the rare occasions when you want to use
the TNC2, you may type "LAN-LINK TNC2" to run LAN- LINK with the
TNC2.SYS configuration file. Make sure you configure that
TNC2.SYS file before you put any signals on the air.
LAN-LINK Memory Requirements
LAN-LINK 2.32 requires a minimum of 450k of RAM. You will need
more RAM if you wish to use the Editor. The Editor files will
each take a maximum of 64K additional RAM. If your memory is
marginal, you may get an error when you try to log a station or
edit a file/message. If you do not have enough memory working
from within LAN-LINK, you may use the EDITOR program from DOS.
PC to TNC Communications
All communications between the computer and the TNC normally use
the 8 BIT NO PARITY and 1 stop bit RS-232 Serial Port
configuration. If you want to limit the character set to the 7
bit ASCII set, set the TNC parameters accordingly. The baud rate
defaults to 1200, but you may set it to 2400, 4800 9600 or even
19200 if your CPU clock is fast enough and the TNC will respond
correctly.
LAN-LINK Runs Open Loop
IF YOU USE LAN-LINK, YOU STILL MUST READ THE TNC MANUAL. WARNING
THIS PROGRAM OPERATES IN AN OPEN LOOP MODE. IT REMEMBERS WHAT
INSTRUCTIONS OR COMMANDS IT GAVE THE TNC. IF FOR SOME REASON, THE
TNC IS NOT SYNCHRONIZED TO THE PROGRAM YOU WILL NOT GET CORRECT
DISPLAYS ON THE SCREEN.
In Case of Problems
In case you have problems, always check the default settings
using the "Verify Changes" option of the Parameters Menu. If you
work CW, read about the XMITOK flag, and set it for the way you
have wired your TNC to the radio. Problems can be caused by
incorrect settings of the TNC parameters. If all else fails,
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 11
(hard) reset the TNC. Make sure XFLOW and FLOW are OFF.
Logbooks
LAN-LINK uses three dBASE 3 compatible logbook files. One is used
for VHF packet logging (VHF.DBF), the second for all HF modes
(HF.DBF) and a third designated as a secondary HF logbook. See
Appendix 2, Section 14 for more information.
How To Get an Update
There are two ways to get an updated version, as follows. When
you register your copy of LAN-LINK, if this version is still
current, your registration will be acknowledged, and the
following upgrade will be sent to you automatically at the time
it is released (in this case, if you move, make sure you notify
me of your new address). If a later version exists at the time
that you register, it will be sent to you when your registration
is acknowledged and you will not be put on the list for an
automatic upgrade.
If you are not on the list for an automatic upgrade (i.e., you
received a disk in the mail as a result of your registration),
then when you hear that a new release is out, do one of the
following:
Send in $5.00 and remind me what size disk to send you.
Download the new version from my land-line BBS or any place else
you find it (You do not need to reregister the upgrade in this
case).
Get it from a friend (You do not need to reregister the upgrade
in this case).
Collect together at least 300 kBytes of traffic on your local
VHF/UHF LAN by running LAN-LINK with the capture-to-disk
activated when you are not connected. If you can add to that,
connect to your local PBBS and dump all current bulletins with
full headers showing date/time into your capture-to-disk file. If
necessary compress the file (ZIP preferred). Send in the disk in
a mailer together with a label addressed to you, and sufficient
return postage, and the upgrade will be yours.
Starting LAN-LINK in a Non Packet Mode
You may start LAN-LINK in a non packet mode, such as Pactor or
Baudot from the DOS command Line. If you wish to do so, the
format of the command is 'LAN-LINK SYSFILE MODE', where SYSFILE
is the name of the LAN-LINK.SYS file or its equivalent, and MODE
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 12
is the letter used in the Communications Menu to put the TNC in
the particular mode (See Appendix 2 Section 20). For example, to
start LAN-LINK in AMTOR from DOS, type 'LAN-LINK LAN-LINK A'. To
start up in Pactor, type 'LAN-LINK LAN-LINK P'.If you are using a
different configuration file, such as HF.SYS, type 'LAN-LINK HF
A' or 'LAN-LINK HF P'.
Using LAN-LINK with a PacketCluster
Connect to the PacketCluster using the Alt-Y key. When the
connection is achieved, and the PacketCluster sends you a ">"
character at the end of a line of text, LAN-LINK will issue the
first cluster command, followed by the second one, to the Packet-
Cluster and return to manual operation. The default commands are
"SHOW/WWV/1" command followed by a "SHOW/DX". Note: PacketCluster
is a specialized PBBS and conference node by Pavillion Software
for DX chasers.
LAN-LINK also sets an internal PacketCluster Flag. When this flag
is set, LAN-LINK will interpret DX announcements, check your hf
logbook and alert you to the status of that prefix in both sound
and color. If you want LAN-LINK to react to the DX Alerts and
search your HF logbook, to see if you have QSLd or Worked or Need
the prefix, customize the Packet Cluster DX Alert Mode in line
112 of the LAN-LINK.SYS file to your liking. The parts of the DX
Alert message will be shown in different colors.
Options in the PBBS/PacketCluster Menu allow you to customize the
check to set up which bands and which modes are checked. For
example if you never work the 160 Meter band, you may customize
LAN-LINK to ignore 160 Meter DX Announcements.
The results of a logcheck show up at the end of the DX Alert
message. LAN-LINK also changes the current band (see status
window) to the band of the call shown in the DX alert.
In the contest Mode, LAN-LINK checks the logbook for the
complete callsign.
"B" means worked on the same band
"W" means worked on another band
"Q" means that the callsign has been QSLd.
In the non contest Mode, LAN-LINK checks the logbook for the
prefix (2 or 3 letters) of the callsign.
"W" means worked on the same band
"w" means worked on another band and
"Q" means that the prefix has been QSLd on the same band
"q" means the prefix has been QSLd on a different band.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 1 Introducing LAN-LINK Page 13
In both contest and non contest modes, a check mark means the
logbook was checked and the prefix not found.
You may use the Alt-G key to grab a DX Alert from the incoming or
scrollback windows. LAN-LINK will set the Radio to frequency and
post the call. This is similar to the action of F10.
You can also enable an automatic QSY to the frequency of a DX
Alert via the Radio Menu.
Using ANSI Color for Transmitting Text Color Files
ANSI control codes are designed to allow you to control the
display at the other end of the link. LAN-LINK 2.32 reacts to
ANSI control codes including the color codes. This feature allows
you to send colorful bragtapes and other files using the text
mode graphics of the PC character set when operating packet,
Pactor or G-TOR.
ANSI color codes are a sequence of characters beginning with the
'Escape' Character (represented as "Esc" or "^[") followed by a [
character, one or two numbers follow and the sequence terminates
with the letter "m". Typical examples are 'Esc [37m' and 'Esc
[40m'. To save time, several codes may be combined using the
semi-colon character as in 'Esc [37;40m'.
When transmitting lines of color, the ANSI control codes add
characters to the line, so your line will probably contain more
than 80 characters. Make sure you set the correct TNC parameter
(i.e. SCREENLN) to 255 to ensure that the TNC doesn't add extra
'CR/LF' codes to your picture and mess it up.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 14
Appendix 2 LAN-LINK Features, Menus and Commands
LAN-LINK provides an interface between you and the TNC. It works
in a client-server mode. It provides you with menus, and then
sends the TNC the commands that you would have had to type to
exercise the particular option. LAN-LINK also provides smart
features to smarten up your packet radio operations.
This appendix contains a summary of the commands and menus
available to you in LAN-LINK. The commands are organized by Menu.
Some function keys provide you with short cuts so you don't have
to go through the entire menus. These function keys are described
below.
1.0 LAN-LINK MESSAGE HANDLING FEATURES
This section describes the mail box and message handling features
built into LAN-LINK.
1.1 Answering Machine
LAN-LINK contains an AMTOR (Robot beacon CQ mode only) and PACKET
Mode SMART "answering machine" facility. You can leave messages
on your disk (in the same directory as the LAN-LINK.* files, if
you are using a hard disk), for different stations. When someone
connects to you, if you left a message for him, he (or she or
even it as the case may be) and only that station will receive it
automatically. No one else will normally be able to download that
message.
1.2 Mail Beacon (Annunciator)
To ensure that people know that you have left a message for them
a "MAIL for" list is loaded into your Packet Beacon and
transmitted every 30 minutes (Refer to the BTEXT command in the
TNC manual) as ":QTC:" followed by a list of calls. If no mail is
pending, or the only message in your system is one addressed to
you, the beacon transmissions are inhibited. This conforms to
good operating practice on crowded channels (at least inhibiting
the beacon does).
The mail beacon in the Pactor, G-TOR, and AMTOR Modes is
transmitted as part of the beacon AUTOCQ message. It is
automatically updated when a message is transmitted. If you don't
set the beacon (see below) you will not transmit a mail beacon
text in your AMTOR CQ message.
The Mail beacon text is set up either when you tell the computer
to set it up or when you disconnect a packet QSO from another
station.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 15
In this manner you may update the list while the program is
running, for example, by using Borland's Sidekick or the included
Editor, to write a message, or preferably the NOTE feature.
Any station using LAN-LINK can be configured to automatically
attempt a connect (QTC-Snatch) when seeing their callsign in
someone else's LAN-LINK :QTC: beacon mail message list.
If for some reason the message got lost (e.g. because the link
was marginal), :QSM: will get you a repeat of that message.
1.3 How to Leave a Message
You can use the "note" feature or type the message as a non-
document file on the included Editor, or if you use another word
processor, you must leave the message as an ASCII text file. In
that case, you just name the message file as the callsign of the
station to whom you wish the message to be sent at connect time.
You must also give it the filetype of "OUT".
For example, a message for G3ZCZ would be stored on the disk as a
file named "G3ZCZ.OUT", and similarly a message to 4X6AA would be
stored on disk as "4X6AA.OUT".
Once the message has been sent, an entry to that effect will be
made in the LAN-LINK.RUN data capture file. The message file will
then be renamed and given the file extension ".OLD". At that time
any previously existing mail file with the file extension ".OLD"
will be deleted. This stops the addressee receiving the message
on successive connects if you can't delete it for some reason
(you forget) while at the same time, the message is still
available to you in case you need it.
You should use a separate utility program if you want the calls
in the mail beacon sorted. You may, for example, wish to sort
them in alphanumeric order, or in the order of the date that they
were left in your answering machine.
Incoming messages triggered by the QTC-Snatch will be left in a
message file named as YOURCALLSIGN.OUT, which can be scanned by
using the Alt-M Key combination. If you have non LAN-LINK
friends, train them to trigger the QTC-Snatch by simulating a
beacon, and prefixing and ending their text with lines containing
the ">" as the only character. Better yet, give them a copy of
LAN-LINK and tell them to use it and register it.
2.0 LAN-LINK WINDOWS
LAN-LINK displays information in different windows. The window at
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 16
the top of the screen is the status window. The big blank window
in the center is the incoming text window. The lower third of the
screen is the outgoing text window. All outgoing text are echoed
in this window. The bottom line is a prompt window.
The indicators in the status line depend on the state of the LAN
Link and are described in the sections that deal with the
functions they are associated with. Some typical status window
displays are shown below.
2 Meters 2 Watts PACKET 1200 W [R] TRFC ->N4QQ
20 Meters 100 Watts MORSE TEST[4]
20 Meters 100 Watts PACKET 300 N TRFC
CAPTURE TO DISK PACKET 300 N [C1][Z] TRFC ->N4QQ
If the automatic Capture-to-disk is turned off, a yellow bug will
be flashing on the left side of the line.
If the Printer Flag is set, a yellow [P] will be flashing on the
left side of the line.
If the miscellaneous flag is set, an asterisk "*" followed by two
numbers and a "]" will be displayed. The first number is the PBBS
Sequence State, the second is the Connect Sequence State. These
numbers reflect the internal state of LAN-LINK and should be
quoted when describing problems.
If a message transfer is taking place, the callsign of the
station involved will be displayed.
When the Capture-to-Disk is turned on, the words "CAPTURE TO
DISK" will be displayed. If it is turned off, the operating band
(Meters) and power (Watts) will be shown. If a Zap PBBS is in
operation, the Bulletin Request Count will then be shown in
square brackets ("[]").
The communications mode will be shown next, it may be one of the
following;
PACKET AMTOR AMTOR-(MAIL) AMTOR-FEC
BAUDOT ASCII MORSE NAVTEX
SIGNAL ???? DEFAULT {boot up}
A flashing yellow musical note following the Communications Mode
indicates that the sound has been inhibited.
The next number to be displayed is the RF communications
baudrate. The letter "W" or "N" indicates that the Wide shift or
the Narrow shift has been selected. A "down arrow" will be shown
if the shift is normal. If the shift is reversed a flashing
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 17
yellow "up arrow" will be displayed.
In the BAUDOT mode, "USOS" will be displayed if unshift- on-space
is selected.
If the Contest Mode is selected, the word "TEST" will then be
displayed followed by the Contest QSO number in "[]".
In certain Robot and AutoCQ states, namely while the computer is
waiting for a reply, a flashing cumulative CQ count will be
displayed next.
If the RTTY SELCAL is active, the word "SELCAL" will be displayed
next.
If the Navy MARS BAUDOT RTTY protocol is enabled, a "[n]" will be
displayed.
In the packet and AMTOR Robot modes, if at least one station has
connected or linked, a flashing yellow "[C]" will be displayed
next. The number in the square brackets with the "C" is the
number of stations that have connected/linked. If the target call
station was one of those station, a happy face will also be
displayed in the square brackets.
If at least one QTC snatch has taken place a flashing yellow
"[Q]" will be displayed next. The number in the square brackets
is the number of QTC Snatches that have taken place.
In the packet communications mode, if a Zap PBBS, a QTC Snatch or
a PacketCluster Zap is in progress a flashing yellow "[Z]""will
be displayed next. However, if LAN-LINK is set to stay connected
when the sequence ends, the flashing indicator will be a "{Z}"
instead of "[Z]".
In the packet or AMTOR communications mode, a "[R]" will be
displayed next if LAN-LINK is configured for store and forward
(:QSP:).
In the packet and AMTOR communications modes, if the beacon mode
is enabled a "[B]" will be flashing yellow. If someone has
connected and sent a :QRT: sequence, the "[B]" will be flashing.
The "[B]" will be followed by a "[M]" if there are messages
pending. The number in the square brackets with the "[M]" is the
number of messages (*.OUT files) pending.
In the packet communications mode, if the SAREX mode is enabled,
a "[S]" will be shown next. The "[S]" will be flashing while
capture to disk is in progress. If SAREX packets have been copied
a happy face will be displayed in the square brackets together
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 18
with the "S". If the SAREX Orbiter robot is active a flashing
">>" will be displayed.
In the packet communications mode, if the digipeat Detect mode is
enabled, a "[D]" will be displayed next.
In the packet communications mode, if connected and ELMER is
active, an "[E]" will be displayed. The number with the "E" shows
ELMER's state.
In the packet communications mode, the terminal sub-modes are
then displayed as follows;
SOLO This lets you only see messages addressed to you.
CQ/B This lets you see beacons and CQ calls as well.
TRFC This lets you see packets containing messages as well.
EVRY This lets you see everything on channel, including the link
control packets.
MAIL This lets you monitor packets from a specific station. In
the PK-232, you can do it without displaying the headers.
Note each mode may not be available in each TNC.
The next item to be displayed is a callsign, under the following
conditions: the call of the station connected with, will be
prefixed by a "*>" when connected, and by a "->" when a connect
request is in progress. If a disconnect is in progress, the
callsign will be replaced by a "$$$$". The callsign will be seen
as flashing when a connect is in progress.
In the MAIL mode, the callsign of the station that you are
"reading the mail" on will be displayed. Otherwise, the callsign
displayed will be that of the one you are connected with.
If an Alert Call has been entered, it will be displayed next.
Similarly, if a Target Call has been designated, the target call
will be displayed next. The display will be slightly different of
the calls have been heard/worked. A "!!>" before the flashing
call indicates that the Alert function is active. A "<->" before
the Alert Call signifies that packets to or from that call have
been heard on frequency. A smiling face in front of the call,
signifies that it has been worked. A "->" is displayed before the
Target Call.
The next items to be displayed are the packet multi user mode
displays. If the conference bridge is up, a flashing yellow
bridge will be shown. If only the conference mode is set, the
letter "C" will be flashing, if the basic multi user mode is set,
the word "M" will be seen. The callsign will be prefixed by the
I/O channel number/letter, and will be in the color allocated to
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 19
the traffic on that channel. The number shown after the flashing
letter is the number of streams that LAN-LINK thinks that you are
connected on.
In the non packet modes, the callsign displayed will be that of
the station being worked (entered by the AMTOR robot, the
automatic CQ call recognition, or by the operator using the Alt-C
or Alt-E keys). In AMTOR, the SELCAL of the other station will
also be displayed sometimes, usually if you entered the call.
An "[L]" will be displayed in the non packet modes when a
callsign is entered. The "[L]" will flash to remind you (to log
it) until the QSO is logged.
3.0 HOT KEYS
LAN-LINK contains a number of "Hot" keys to allow you to perform
common operations with a minimum of key strokes. The keys perform
related but slightly different tasks in each communications mode.
A list of those available is shown in Table 3-1. Should you
require any more hot keys, I suggest you use an external program
with a Keyboard Macro capability such as Borland's Superkey.
Consider the action of each key in detail.
3.1 Alt-A Alert Call (Packet) and AMTOR ARQ Call/Talk
In the Packet Communications Mode, this key combination performs
the same task as the Alert Call option in the Call Menu.
In AMTOR, this key combination will attempt to send an ARQ call
to the desired station, transmit the callsign sequence when
linked and allow you to continue typing text (i.e. it will not
transmit the "+?" characters). Use this command option to log on
to an APLINK PBBS.
3.2 Alt-B Send Break/AMTOR Changeover
In the Packet Communications Mode, activating this key
combination sends a "BREAK" signal to the TNC. Use this key
combination to get out of the TNC's transparent mode.
In the AMTOR Communications Mode, use this key combination to
force a changeover. You can type text into the outgoing buffer
and then force a changeover without losing that text.
3.3 Alt-C Call/Connect to Someone
This key combination works in almost the same manner in both the
packet and non packet communications modes as described in the
following sections.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 20
Table 3-1 LAN-LINK Hot Keys
Hot Key Communications Mode
_______________________________________________________________
Packet AMTOR/Pactor/G-TOR BAUDOT/ASCII CW
____________________________________________________________________
A Set ALERT Call ARQ Call/Talk ------ ------
____________________________________________________________________
B Send 'Break to TNC' Force Changeover ------ ------
____________________________________________________________________
C Connect ARQ Call Call Call
____________________________________________________________________
D Disconnect Toggle Receive Modes Receive Mode Disengage Lock
____________________________________________________________________
E Enter Call Enter Call and Selcal Enter Call Enter Call
____________________________________________________________________
F Flush TNC Buffer (all communications modes)
____________________________________________________________________
G Grab Call and frequency (PacketCluster Flag set)
____________________________________________________________________
H Display function key Information Screen
____________________________________________________________________
J Jump to DOS (all communications modes)
____________________________________________________________________
K PacketCluster Spot
____________________________________________________________________
L Edit Log Entry (all communications modes)
____________________________________________________________________
M Scan Message (all communications modes)
____________________________________________________________________
N Next I/O Stream
____________________________________________________________________
O Turn Robot ON Turn Robot ON ------ ------
____________________________________________________________________
P Turn Printer ON/OFF (all communications modes)
____________________________________________________________________
Q call QRZ call QRZ in FEC call QRZ call QRZ
____________________________________________________________________
R Retry Connect Retry last Call (entered).
____________________________________________________________________
S Scan Logbook (all communications modes)
____________________________________________________________________
W :QRA: ---------- ------- ------
____________________________________________________________________
X Exit to DOS (all communications modes)
____________________________________________________________________
Y Zap PacketCluster ---------------- Transmit RY's -----
____________________________________________________________________
Z Zap BBS Drop Link after Receive mode after
after sending contents of buffer
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 21
____________________________________________________________________
3 Set foreground color in outgoing text
____________________________________________________________________
4 Set background color in outgoing text
____________________________________________________________________
3.3.1 Non Packet Modes
You use this key combination to call a station heard on the band.
In AMTOR the link request will be sent in the ARQ Mode to the
SELCAL of the desired station. (Note that this option sends the
"+?" after the callsign sequence).
3.3.2 Packet Mode
You use this key combination to attempt a connect with another
packet station. In a multiconnect situation the LAN-LINK will
auto-matically select a free I/O channel to try the connect.
3.3.2.1 Names, Handles and Paths: If you so desire, you can
create a directory file (default name is LAN-LINK.DIR)
and keep a list of names and calls. The computer will
look up a name and call the station by its callsign. For
example if you put "Joe G3ZCZ" as a line in the file,
when you tell the computer to connect to Joe, it will
try to connect to G3ZCZ. If you enter " 4X4HF 4X4HF V
4X1AA, 4Z4ZB, 4X4IL" on a line in the file, you only
need to type "4X4HF" to set up the correct connect path.
You can also use this feature to automate a NET/ROM
and/or a KA-Node path connection.
3.3.2.2 Loop Backs: In the Packet Communications Mode, if you
want to loop back through someone else you would have to
type "C YOURCALL VIA OTHERCALL" to the TNC. For example
if I wanted to loop back through 4X6AA, I would have to
type the command "C G3ZCZ VIA 4X6AA" to the TNC.
In LAN-LINK you just have to enter the "/" character
followed by the call of the station you want to loop
back through. For example if I wanted to loop back
through 4X6AA, I just need to enter "/4X6AA" as the call
to connect to at the correct prompt, and LAN-LINK will
tell the TNC to try to connect to G3ZCZ via 4X6AA,
namely issue the command "C G3ZCZ VIA 4X6AA" to the TNC.
3.4 Alt-D Disconnect or Receive
This key combination performs the same task as Function Key 8
(F8) EXCEPT in MORSE and AMTOR.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 22
In the Morse communications mode, this key disengages the receive
speed lock in the PK-232 to unlock the PK-232 from the last
signal copied. It lets you lock onto another signal faster.
In AMTOR this key toggles the receive mode between ARQ and FEC
signals (QSO's in progress and CQ calls).
3.5 Alt-E Enter Call
This key combination lets you enter the call of any station
calling you into the program. If you type the Enter Key in
response to the prompt, you can later use Function Key (F3) to
transmit the sequence "DE YOURCALL". You may also use the Retry
feature to call that station.
In AMTOR, you use the feature to enter the callsign and SELCAL of
the station you are listening to and may want to call later.
3.6 Alt-F Flush TNC Buffer
This key combination performs the same task as the Flush TNC
Outgoing buffer option in the TNC Menu.
3.7 Alt-H Help Information for Function Keys
This key combination lets you display a brief reminder of the
action of each hot key. It performs the same function as the "H"
option in the Main Menu.
3.8 Alt-J Jump to DOS
This key combination lets you "Jump to a DOS Shell". It performs
the same function as the "J" option in the Main Menu.
3.9 Alt-K PacketCluster DX Alert
This key combination initiates the PacketCluster DX Alert sequence
described in the BBS Menu.
3.10 Alt-L Log Contact
This key combination appends the callsign for the current QSO to
the Log.
3.11 Alt-M Message Scan
This key combination performs the same task as the Message Scan
choice in the Message Menu.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 23
3.12 Alt-N Next Stream
In the Packet Communications Mode, if you are using the multiple
connect capability of LAN-LINK, this key combination prompts you
to change I/O streams, and display the state of the I/O streams,
showing which ones were last used to send or receive something.
To change I/O streams, move the cursor to the desired stream then
push the "Enter" Key. The calls in the Next Stream window update
when stations connect and disconnect. In the event of the window
not being correct, you may manually enter or delete calls using
the "Insert" Key to enter a call, and the "Delete" Key to remove
a call.
The data about the streams will be shown in the same colors as
the multi-stream text colors.
3.13 Alt-O Turn Robot On
This key combination performs the same function as the Set ROBOT
option in the AMTOR Terminal Menu. The hot key combination
however, is active in both the Packet and AMTOR communications
modes.
This function key also puts the Packet and AMTOR Contest
operation into automatic.
3.14 Alt-P Turn Printer ON/OFF
This key combination performs the same function as the toggle
printer on/off option in the Parameter Menu.
3.15 Alt-Q Call QRZ
This key combination transmits the sequence "QRZ QRZ QRZ DE
YOURCALL" and turns the transceiver back to receive. In AMTOR, it
sends the sequence in FEC and adds the SELCAL.
3.16 Alt-R Retry Call/Connect
This key combination allows you to retry a connect that for some
reason did not go through the first time. It saves wear and tear
on your fingers particularly if the desired connect path is via a
number of digipeat relays or through a number of Nodes.
In the non packet modes, it allows you to retransmit a call to
another station without having to re-enter the call.
If you have previously used the "Enter Call" feature to put a
callsign in the program when you hear that station, you can use
the Retry command to call him later when the QSO in progress
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 24
terminates.
3.17 Alt-S Scan Log
This key combination performs the same function as the Scan
option in the LOG Menu.
3.18 Alt-W :QRA:
In the Packet Communications Mode, this key combination performs
the same task as the "W" option in the LAN-LINK menu. It puts the
TNC in the converse mode, sends a ":QRA:" and returns the TNC to
the command mode.
3.19 Alt-X Exit to DOS
This key combination performs the same task as the Exit to Dos
choice in the Main Menu. It exits the program and returns you to
DOS.
3.20 Alt-Y Zap PacketCluster/RTTY Transmit "RY"s
In the Packet Communications Mode, this key combination first
prompts you with the callsign of the PacketCluster. If you enter
a callsign, the entered callsign will become the new Packet-
Cluster call. LAN-LINK then issues a connect request to the
PacketCluster. In the RTTY communications mode, this key
combination causes a sequence of "RY"s to be transmitted.
3.21 Alt-Z Zap PBBS
In the Packet Communications Mode, the Alt-Z key initiates a PBBS
Mail Snatch. You use this key if you connect to a PBBS before you
hear its beacon, or if you have disabled the PBBS Mail Snatch
feature. If you are connected to a PBBS, the key must be used
BEFORE the first ">" is received. The first ">" triggers the
sequence. If you have already received that first ">", send the
PBBS any command, and the sequence should begin when the PBBS
signals that it has completed processing that command. If you are
not connected, LAN-LINK will first try to connect to the PBBS,
then perform the sequence.
When you use this command you will be asked if you want to upload
or download. If you want to download, just push the "Enter" Key.
A Download (Mail from the PBBS to you) will automatically be
followed by an Upload if the *.BBS file exists.
The download default sequence performed by the PBBS Mail Snatch
is as follows:
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 25
RM To read your messages, (Configurable)
L To let you know what is new on the PBBS,
LM To list ALL your messages on the PBBS,
B To log you off the PBBS.
LAN-LINK will wait for the ">" as the last character of the line
of text being received from the PBBS, before issuing the next
command in the sequence. Your messages will be placed in a
message file YOURCALL.OUT as if someone else had left a message
for you.
The "RM" may be customized in the LAN-LINK.SYS file to "RN" or
"VM" depending on the software in your local PBBS, and, on your
preference.
During the time that the PBBS is responding to the "L" command
with a list of new messages, LAN-LINK is scanning the lines
containing the messages to see if it finds one containing a Scan
Word. If it does it will queue a request to download that
message. The line of text will also be displayed in a color that
matches the colors those scan words are shown in the window
generated by exercising option W in the Parameter Menu.
The PBBS Mail Snatch can be initiated in two ways. It can be
initiated when your incoming screen displays a "Mail" beacon
(received from your local PBBS) with your call in the first line
following the header, or by LAN-LINK's Zap PBBS function (this
key combination). The automatic PBBS Zap will not take place if
LAN-LINK is in the multi-user mode.
In the event of a PBBS Mail-Snatch, if the *.BBS file exists for
that PBBS, the file will be processed and the contents sent to
the PBBS. Thus if you don't get a chance to send the mail before
LAN-LINK downloads the mail from the PBBS, it will send it for
you.
When the PBBS has accepted the commands the name of the file is
changed from "*.BBS" to "*.n", where "n" is a number increasing
sequentially each time the function is performed from a base
value set up in the LAN-LINK.SYS file. For example, the file name
KE8X.BBS will be changed to KE8X.001 the first time it happens.
In this way, you will have a copy of the outgoing file on your
disk until you choose to delete it.
In the real world however, message formats are nonstandard, and
can contain any set of characters. The algorithm developed here
transmits the next line in the *.BBS file when LAN-LINK sees a
"trigger" character string unless one of the "inhibitor"
character strings is also present on the line of the message text
received by LAN-LINK.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 26
These "trigger" character strings are ">" (as the last character
of the line of text), and the customizable ones such as "Enter",
"Subject", "Sj:" and "Msg:". The "inhibitor" character strings
are "R:", "<" and "Message" ("R:" as in routing headers and "<"
and "Message" as in Message-Id: <message number> in message
headers).
This should cover most simulated manual PBBS message reading
(WA7MBL and W0RLI/VE3GYQ) and avoid false triggering due to ">"s
showing up in message and routing headers.
When LAN-LINK finishes processing the *.BBS file, it will send a
"B" command to the PBBS to terminate the session. This PBBS Zap
feature is designed to minimize the time you spend connected to
the PBBS by allowing you to scan the message list when automat-
ically receiving your mail, prepare your replies, and download
requests off-line and then later read the incoming messages or
files without tying up the PBBS. For this reason, it thus
disconnects you from the PBBS. You can, however, override the
automatic disconnect command for the duration of the connection
using the "F" option in the Parameter Menu.
3.22 Alt-= Toggle Miscellaneous Flag
This key combination performs the same function as the "+" option
in the parameters menu.
3.23 End "> +?" [Over]
In the Packet Communications Mode this command sends your
callsign followed by the ">" and "Carriage Return, Line Feed"
character combination. You may use this to signal "OVER" in a
packet contact.
In the AMTOR Communications Mode this command sends the "+?"
sequence of characters which is the software "OVER" signal. LAN-
LINK will change colors when it recognizes the '+?' in the
incoming window.
In the Pactor Communications Mode this command sends the "=>"
sequence of characters and switches the link to allow the other
station to send. LAN-LINK will change colors when it recognizes
the '=>' in the incoming window.
In the MORSE and RTTY (BAUDOT and ASCII) communications modes,
this command lets you transmit the "KN" sequence and returns you
to the Receive Mode. LAN-LINK will change colors when it
recognizes the 'KN' in the incoming window. In these modes there
is no standard for signaling 'over'. The 'KN' sequence may show
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 27
up in text (i.e. in the word KNOW) or in a callsign (i.e. G9KNA)
and cause a color change. If this "random" color change bothers
you in BAUDOT, change line 114 in the LAN-LINK.SYS file from KN
to some other pair of characters that should not show up in
normal text.
If you have typed something into the "type ahead buffer" and then
press this key, the contents of the buffer will be transmitted
followed by the turnover command.
For example, if you are 4X6AA, and you are working G3ZCZ, then
you would use Function Key 3 (F3) to transmit the sequence "G3ZCZ
de 4X6AA" and this key to send "over" and revert to receive.
3.24 PgUp Scrollback (Scrolls back incoming text)
This key lets you repeat the display of up to 412 lines of
incoming text which has scrolled out of the incoming window. You
may print it or capture it to disk during the repeat.
The bottom line menu displays your options when showing the
scroll back information. Use the "Escape" key to terminate the
Scrollback Mode.
You can save the contents scrollback buffer displayed on the
screen by turning the "Capture-to-Disk" on, and then writing text
to the window. Anything written will be captured. If the Capture-
to-disk is ON before or during scrollback, you will get two
copies of the text in the file.
3.25 The Home Key
The Home Key will clear the window screen that the cursor happens
to be in at the time that the key was depressed, and will then
position the cursor at the top left hand corner of that window.
3.26 The Down Arrow Key
The Down Arrow Key toggles the Normal/Reverse Sideband command in
all communications modes except MORSE. The sideband is depicted
in the status window by the "Up" and "Down" arrows. If the "Down"
Arrow is showing, you are set for Lower Sideband (LSB) which is
the one normally used.
If you set your transceiver to LSB, you will be set correctly for
all modes. If you have reversed the sidebands, a flashing "Up"
Arrow will be displayed. For CW operation you may set your rig to
the CW position and ignore the sideband setting. If you use FSK,
just set it so that it works for you.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 28
3.27 Shift/Baudrate Control Keys
The following keys are used to control the Shift (Wide or narrow)
and the Radio link baudrate in the BAUDOT and ASCII
communications modes. In the BAUDOT and ASCII communications
modes all baud rates supported by the PK-232 may be selected.
3.27.1 RIGHT ARROW: This key speeds up the baud rate. In the CW
communications mode, the right arrow increases the CW
speed by 1 wpm.
3.27.2 LEFT ARROW: This key slows down the baud rate. In the CW
communications mode, the left arrow decreases the CW
speed by 1 wpm.
3.27.3 UP ARROW: This key toggles the shift from Wide shift (850
Hz) to Narrow shift (170 Hz) and back. If you are using
a KAM, it will also pass through the 425 Hz shift
position.
3.27.4 DELETE: This key toggles the USOS command (RTTY only).
The state of each of the above commands are displayed in the
status window at the top of the screen. If USOS is active, "USOS"
will be shown. The shift is shown as "W" or "N" for wide or
narrow respectively.
3.28 Control-Z (^Z)
This key combination is used in the Packet Communication Mode to
signal the end of a file or message, when loading messages into
another LAN-LINK system or into a PBBS. In the AMTOR Communica-
tions Mode, it is automatically translated into the sequence "
:EOF: +? " which can be used to terminate a message being stored
in another LAN-LINK AMTOR mailbox.
3.29 Control T (^T)
This key combination inserts the date-time-text string into the
outgoing buffer. A typical example is "11-Mar-93 01:39".
4.0 FUNCTION KEYS
Function keys are used to perform operations common to all
communications modes, or to allow fast performance of a function
without having to go through several layers of menus. The action
of each of the function keys is described in the following
sections. The function key number corresponds to the paragraph
number, namely 4.1 refers to Function Key 1 (F1), etc.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 29
4.1 Capture to Disk Toggle (F1)
This key toggles the "capture-to-disk" command. When the
"capture-to-disk" is active, all incoming text (including "Echo
as sent" outgoing text) is stored on a disk (floppy or hard) in a
file called "YYMMDD.RUN" where YY is the last two digits of the
year, MM the month and DD the day (E.G. 900824.RUN). If this file
does not exist the first time that LAN-LINK is loaded, it is
created. From that time on, for the rest of that day, successive
activations append new data to the contents of the file.
Each time the command is activated a datestamp (or timetag) will
be written to the file.
When a Packet station connects "capture-to-disk" will be
activated automatically unless you instruct LAN-LINK not to do so
with the Capture-to-disk flag. Packet connects will thus be
recorded in their entirety automatically unless you turn off the
"Capture-to-disk" during the course of the QSO. "Capture-to-disk"
will be stopped at disconnect time.
You may later edit the file at your convenience with your
favorite word processor or the included Editor. However, if your
word processor can only handle files smaller than 64k, make sure
that the "capture-to-disk" file remains smaller. You can do this
by renaming the file to something like "LAN-RUN.001". LAN-LINK
will automatically close the "capture-to-disk" file when you
terminate the program and return to DOS.
You can make Capture-to-disk active when you scroll back. You can
use this feature to save data that has already scrolled by the
window.
4.2 Send Brag Tape and Talk (F2)
This command lets you transmit the Brag Tape (Default LAN-
LINK.TXT). In the non packet modes, it will leave the transmitter
on after sending the file. In the packet mode it will send a ^Z
after sending the file to notify the recipient that the file is
complete.
4.3 Transmit Callsign Sequence (F3)
This command lets you transmit the following sequence OTHERCALL
DE YOURCALL. For example, if you are 4X6AA, and you are working
G3ZCZ, then this command would transmit the sequence "G3ZCZ de
4X6AA". You may use this key at the start and end of a
transmission in any mode except Packet.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 30
4.4 Send Brag Tape (F4)
This command lets you transmit the Brag Tape (Default LAN-
LINK.TXT). In the non packet modes, it will turn the transmitter
off after sending the file.
4.5 Show Packet "MH" list and Point and Shoot Connect (F5)
This command lets you see what calls the TNC has heard recently
on the Packet channels. You can see up to 18 callsigns, with the
date and time they were last logged by the TNC. Refer to the "MH"
command in the TNC manual for the particulars of the display.
The MH list shows up in a special window and freezes until you
depress any key. While the list is frozen, LAN-LINK is not
monitoring received data, so don't freeze it too long.
When you activate F5, LAN-LINK redirects all data coming from the
TNC into the MHwindow. If the MH list is blank, or information
comes in from the TNC between the time you entered the command
and the time the list is sent back, subsequent text from the TNC
will show up in the MH window until the next "Cmd:" appears or 18
lines of text have been received.
You can also use this command in a point and shoot method for
attempting a connect with a station you have heard. Bring up the
MH Window and move the cursor to the desired callsign. When the
cursor is positioned on any character in the call, press the
"Enter" Key and that call will be recognized as the callsign. If
the call is joined to the word "Cmd:" or the cursor is positioned
on a space or blank, the connect attempt will be inhibited.
LAN-LINK has no way of knowing when the MH list is complete.
Consequently, it sends two commands to the TNC to implement this
feature. The "MH" command instructs the TNC to start sending the
MH List, the "ZCZ" command forces an error response from the TNC.
LAN-LINK uses the error response to close the MH Window.
This command does not work on the TNC1.
4.6 Auto CQ Call (F6)
This command will send a CQ sequence, wait a presettable delay
and then repeat the CQ sequence until it receives your call back
from someone else. When it does so, it will alert you with a
Connect Alarm signal, reset the delay timer, and revert to the
normal or listening mode. In AMTOR it will revert to the mode in
which it is waiting for an ARQ call and is able to copy FEC
signals on frequency.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 31
When the Automatic CQ sequence is in operation, an indication
will be shown in the status window. The indicator will be steady
while the transmitter is sending the CQ text, and will blink
while the receiver is listening for a reply.
The time delay between calls is set using the "Q" command in the
Parameters Menu (Set CQ delay time). It is also set as a defined
default by you when you setup your LAN-LINK.SYS file.
The automatic CQ command will only work in the TNC non packet
modes if the "Echo as Sent" parameter is set to "ON" per the LAN-
LINK.SYS file. In other words, you must be able to see the CQ
text slowly echo in the incoming window for the command to work.
This is because the "K K K" (or "+?" in AMTOR) sequence is used
to arm the software to look for a reply.
In AMTOR you will get the connect alarm only when the replying
station transmits the "+?" character combination.
The check for the detection of your callsign and the connect
alarm sequence only occur after a line feed character has been
received.
Under most conditions in AMTOR, many in RTTY, and some in MORSE,
LAN-LINK will recognize the callsign of the station answering
your CQ and display it in the status window. In the event that it
fails completely, the sequence "--?--" will show up in the status
window. Since the callsign recognition algorithm used just looks
for the first word following the "DE space" sequence and assumes
that it has the callsign, be careful to check it when operating
under QRM conditions. You can override the automatic call
selection with the Enter Callsign command in the Call Menu.
The automatic CQ sequence is canceled when an incoming call is
detected (only if the Beacon or Robot-Mailbox Mode is not
selected), if you push the disconnect command key, the "End" key,
F3, or if you change communications modes.
4.7 Activate Type Ahead Buffer/AMTOR Relink (F7)
This key is not available in the Packet Communications Mode. It
also functions somewhat differently in the AMTOR and other
communications modes as described in the following sections.
4.7.1 Activate Type Ahead Buffer
The use of this key sets LAN-LINK to the "Type Ahead" Mode. This
is necessary for the PK-232 only, the KAM and the MFJ1278 have
the feature built in. Any characters then typed at the keyboard
will be placed into the TNC transmit buffer. The contents of the
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 32
buffer will be transmitted over the air when the transmit command
is invoked with Function Key 10 [F10].
This feature allows you to "type ahead" as you can enter text
into the transmit buffer while viewing incoming words in the
INPUT window in the screen. Any characters typed from the
keyboard will be echoed in the OUTGOING window on the screen.
4.7.2 AMTOR Relink
If you return to the Command Mode when linked to another station
in AMTOR, use this key to get back to the Converse Mode. If the
link times out, you can try to relink with this key if you have
entered the SELCAL of the other station.
4.8 Disconnect, Disengage or Receive (F8)
This function key returns the station to the receive communi-
cations (TNC command) mode. It may also be used to abort the
automatic CQ sequence. If you use it to abort a CQ sequence while
the transmission is in progress, you may also want to flush the
PK-232 transmit buffer by using the Flush command in the TNC Menu
or the Alt-F hot key combination.
In a multi-connect situation the program will prompt you to tell
it which I/O channel to disconnect.
In AMTOR this command key toggles LAN-LINK between the Chirpcopy
Mode (listening to a QSO in progress) and monitoring FEC
transmissions (CQ calls).
4.9 Put TNC in CMD Mode (F9)
This command puts the TNC into the Command Mode. At this time,
the program is transparent and acts as a dumb terminal (except
for placing incoming and outgoing text in the relevant windows).
You use this Mode for overriding any of the TNC default
conditions. (See I told you that you had to read the TNC
manual).
4.10 Put TNC in CONVERSE/Transmit/AMTOR FEC (F10)
This command places the TNC into the transmit or Converse Mode.
The transmitter is turned on and the contents of the transmit
buffer are transmitted. In the non packet communications modes,
the outgoing characters will be echoed back from the TNC and
displayed in the INCOMING window on the CRT as they are
transmitted on the air. In the AMTOR communications modes, this
key puts the TNC in the FEC Mode and turns the transmitter on.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 33
4.11 Alternate Function Keys
These keys transmit the files with the fixed names LAN- LINK.001
through LAN-LINK.010 (the suffix number corresponds to the
function key). These files must be located in the same sub-
directory as the LAN-LINK.EXE program. The transmitter is left on
when the file has been sent.
4.11.1 Send/Talk file LAN-LINK.001
4.11.2 Send/Talk file LAN-LINK.002
4.11.3 Send/Talk file LAN-LINK.003
4.11.4 Send/Talk file LAN-LINK.004
4.11.5 Send/Talk file LAN-LINK.005
4.11.6 Send/Talk file LAN-LINK.006
4.11.7 Send/Talk file LAN-LINK.007
4.11.8 Send/Talk file LAN-LINK.008
4.11.9 Send/Talk file LAN-LINK.009
4.11.10 Send/Talk file LAN-LINK.010
If the Mode File Flag is set (see 10.14), the file names will
change according to the modes.
In the non packet communications modes, the transmitter is left
on when the file has been sent. In AMTOR, the changeover
character pair (+?) is not sent.
4.12 Shift Function Keys
These function keys show the contents of the files with the fixed
names LAN-LINK.001 through LAN-LINK.010 (the suffix number
corresponds to the function key). These files must be located in
the same sub-directory as the LAN-LINK.EXE program.
4.12.1 Show contents of file LAN-LINK.001
4.12.2 Show contents of file LAN-LINK.002
4.12.3 Show contents of file LAN-LINK.003
4.12.4 Show contents of file LAN-LINK.004
4.12.5 Show contents of file LAN-LINK.005
4.12.6 Show contents of file LAN-LINK.006
4.12.7 Show contents of file LAN-LINK.007
4.12.8 Show contents of file LAN-LINK.008
4.12.9 Show contents of file LAN-LINK.009
4.12.10 Show contents of file LAN-LINK.010
If the Mode File Flag is set (see 10.14), the file names will
change according to the modes.
4.13 Control Function Keys
These function keys show the first lines of the files with the
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 34
fixed names LAN-LINK.001 through LAN-LINK.010 (the suffix number
corresponds to the function key). These files must be located in
the same sub-directory as the LAN-LINK.EXE program.
If the Mode File Flag is set (see 10.14), the file names will
change according to the modes.
5.0 THE MAIN MENU
When you press the "Escape" Key, the Main Menu shown in Figure 5
appears on your screen and provides you with a number of choices
as described in the following sections. Type in the single letter
to make your choice.
Figure 5 Main Menu
A Quick Menu
B PBBS Menu
C Call Menu
D eDit Menu
E Event/Clock Menu
F Files Menu
H Help with Function keys
J Jump to DOS Shell
K Lan-linK Menu
L Log Menu
M Message Menu
N TNC Menu
O AMSAT-OSCAR Menu
P Parameter Menu
Q Q Codes [NC/L]
R Radio Menu
S communicationS Mode Menu
T Terminal Mode Menu
X eXit LAN-LINK
Z Elmer Menu
Different options will show up in each menu depending on the
connect state (in packet) or the type of TNC that you are using.
For example, if you are using a TNC that only supports packet,
the non packet menus will not be seen. The PBBS Menu is only
active when you are connected to another station.
5.1 The Quick Menu
The Quick Menu shown in Figure 5.1 is designed for new users and
provides the most commonly used functions in a single Menu. Type
in the single letter to make your choice. Each option is
described below.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 35
Figure 5.1 The Quick Menu
A Auto CQ
B Send Brag Tape
C Connect to Someone
I Initialize PK232
L Log
M Change Mode
Q Call CQ
S Send File
T Send File/Talk
Z QRZ
1..0 Send/Talk 1..10
5.2 Auto CQ
This option initiates the automatic CQ sequence in which LAN-LINK
sends out a CQ call, listens for a reply, and if none is
received, sends out another CQ call, and so on, ad infinitum. It
is the same as using Function Key 6 (F6).
5.3 Send Brag Tape
This option transmits the Brag Tape is the same as using Function
Key 2 (F2).
5.4 Call Someone
This option is used when you want to call or connect to another
station.
5.5 Log Menu
This option invokes the logbook.
5.6 Change Communications Mode
This option invokes the Communications Mode Menu. You use it to
change TNC communications modes.
5.7 Call CQ
This option is used to initiate a single CQ call.
5.8 Send/Talk File
This option is used to send a file. When the file has been sent,
the transmitter will stay on. This option performs the same
function as Function Key 4 (F4).
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 36
5.9 QRZ
This option is the same as using Alt-Q Function Key (Alt-Q).
5.10 Send/Talk LAN-LINK Files 001..010
This option is used to transmit the contents one of the LAN- LINK
buffer files. You select the number, LAN-LINK does the rest. The
option is the same as that provided by the Alternate Function
Keys.
6.0 THE PBBS/PacketCluster Menu
The PBBS menu shown in Figure 6 gives you smart file transfer
capabilities with a PBBS. The menu is only active when you are
connected to another packet station. Type in the single letter to
make your choice.
Figure 6 PBBS Menu
D Download Text File
X Download Binary File (Xmodem)
Y Download Binary File (Ymodem)
C Zap PacketCluster
P Zap PBBS
K Turn PacketCluster Mode OFF
D Send DX Alert
1 Clear All Search Flags
2 Set All Search Flags
3 Set All CW Search Flags
4 Set All SSB Search Flags
5 Set/Clear Individual Search Flags
6 Set/Clear Current Band Search Flags
6.1 Download Text Files
This option lets you download a text file from the PBBS into a
separate text file on your disk. Enter the full PBBS download
command at the prompt line.
To download a file from a W0RLI PBBS such as FILENAME.TYP in the
"A" sub-directory you'd enter "DA FILE- NAME.TYP". To download
the same file from the PACKET sub-directory of a WA7MBL PBBS
you'd enter the command "D \PACKET\FILENAME.TYP".
If you use the "D" command to download a text file, it will end
up in a separate file on your disk ONLY IF a file of the same
name does not exist on your drive. If a file with the selected
name already exists on your disk drive you will get an error
message.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 37
6.2 Download Binary File (Xmodem)
This option lets you download a binary file from the PBBS or
other packet station using the Xmodem protocol into a separate
text file on your disk. You have to configure the Xmodem Receive
Batch file before you use this command.
When you use this command, you first have to tell the PBBS the
name of the file you are going to download, and then bring up
this option to tell LAN-LINK that a binary file is on its way.
LAN-LINK uses an external binary file transfer protocol to do the
actual file.
6.3 Download Binary File (Ymodem)
This option lets you download a binary file from the PBBS or
other packet station using the Ymodem protocol into a separate
text file on your disk. You have to configure the Ymodem Receive
Batch file, before you use this command.
When you use this command, you first have to tell the PBBS the
name of the file you are going to download, and then bring up
this option to tell LAN-LINK that a binary file is on its way.
LAN-LINK uses an external binary file transfer protocol to do the
actual file.
6.4 Zap PacketCluster
This option is the same as the Alt-K function key.
6.5 Zap PBBS
This option is the same as the Alt-Z function key.
6.6 Turn PacketCluster Mode ON/OFF
This option turns the PacketCluster Mode ON and OFF. If the flag
is on LAN-LINK will scan the incoming lines for a DX Alert
message.
You may monitor a PacketCluster in the TRAFFIC mode. When a
DX Alert shows up, it is sent to each connected station in turn.
LAN-LINK will only interpret the first one.
LAN-LINK displays the parts of the DX Alert message in different
colors. The colors correspond to the Multi String Colors, shown
in the color option in the Parameter Menu.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 38
6.7 Send DX Alert
This option is the same as the Alt-K function key. Use it AFTER
you have made the contact.
If you have a valid Radio, LAN-LINK will read the frequency from
the Radio. If not, LAN-LINK will prompt you to enter the
frequency. LAN-LINK will then prompt for the call of the DX
Station, and will assume that you want to send the call of the
one you have just logged.
6.8 Clear All Search Flags
This option clears all the band search flags. LAN-LINK will not
check any bands. These options are provided for fast temporary
changes when working a contest.
6.9 Set All Search Flags
This option sets all the band search flags. LAN-LINK will check
every band.
6.10 Set All CW Search Flags
This option sets all the CW band search flags. LAN-LINK will
check every CW band.
6.11 Set All SSB Search Flags
This option sets all the SSB band search flags. LAN-LINK will
check every SSB band.
6.12 Set/Clear Individual Search Flags
This option prompts you to set or clear each flag for each band
6.13 Set/Clear Current Band Search Flags
This option allows you to set or clear the search flags for the
band you are operating on. Use this option and the "clear all"
option in a contest to change settings when changing bands.
Notes:
1: Use the Update option in the Parameter Menu to save the state
of the individual flags permanently.
2: Set the debug flag on, to verify the prefix, if you are think
LAN-LINK is incorrect in its searches.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 39
7.0 THE CALL MENU
The call menu is used to enter calls, either to call/connect/link
a station or to remember a call or path. Each time you are
prompted for a call, LAN-LINK will remember the previous 15 calls
and you may use the Up and Down arrows to move the cursor to a
remembered call. If you wish to capture a call from the incoming
text window, push Function Key 10 (F10) to enter the incoming
text window and move the cursor to the desired callsign. When the
cursor is positioned on any character in the callsign, push the
"Enter" Key and that word will be recognized as the callsign. Any
characters joined to the call (such as a ".") will be picked up
as part of the call. If the cursor is positioned on a space or
blank, the connect attempt will be inhibited.
In AMTOR, whenever you are asked to enter a callsign, LAN-LINK
will prompt you with its guess at the SELCAL. If you agree with
it, just press the "Enter" Key, if you disagree, enter your
choice over the prompt version.
The Call Menu is communications mode sensitive. It gives you
different choices in each communications mode. In the packet
communications mode it provides the choices shown in Figure 7.1.
In AMTOR, it provides the choices shown in Figure 7.2. Type in
the single letter to make your choice.
7.1 Alert Call
This option toggles the Alert call feature ON and OFF. If it is
off, you are prompted for the call to be monitored, and, if it is
on, it is turned off. The toggle is set when you enter a
callsign, and cleared when you depress the "Enter" Key instead of
a callsign.
Figure 7.1 The Packet Mode Call Menu
A Alert Call
D Show Directory
M ReMember Path
P Packet Cluster
T Target Call
Q Call CQ
U aUto CQ
! Zap PBBS [on Beacon]
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 40
Figure 7.2 AMTOR Mode Call Menu
D Show Directory
Q Call CQ
U aUto CQ
X Turn DX ON
The Alert call will be shown flashing in the status window when
in the disconnected state.
The Alert call feature is used in the Packet Communications Mode
when disconnected and the terminal set for "TRFC" or "CQ/BEACON".
LAN-LINK will scan the packet headers received from the TNC, and,
when it sees a packet originated (or digipeated if the MRPT
parameter in the TNC is set to "ON"), by the station whose call
you have entered as the "Alert" call, it will sound an alarm at
the console. The line containing the packet header will also be
displayed in the Alert call color. If the terminal is set for
"CQ/BEACON" the Alert will only sound if the specified station
transmits CQ or BEACON packets.
7.2 ReMember Path
You may use this option to put an entry in the LAN-LINK.DIR file.
7.3 Call CQ
You use this command key to call CQ. In the Packet Communications
Mode, the TNC will transmit a line of text along with the CQ
packet. The line of text is in line 3 of the LAN-LINK.SYS file.
In the AMTOR Communications Mode, your SELCAL will be transmitted
along with the CQ call in the FEC Mode.
7.4 Show Contents of Call Directory
This option displays the contents of the call directory file
(LAN-LINK.DIR). Use this option to verify the contents of the
file.
7.5 Target Call
This option toggles the Target call feature ON and OFF. If it is
off, you are prompted for the callsign to be detected. If it is
on, it is turned off. The toggle is set when you enter a
callsign, and cleared when you press the "Enter" Key instead of a
callsign.
The Target call feature is used in the Packet Communications Mode
when disconnected. LAN-LINK will monitor the stations connecting
to you. When it sees a connect by the station which you have
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 41
entered as the "Target" call, it will set the flashing Connect
Count display to show a "happy face". The Target call will be
shown flashing in the status window when in the disconnected
state.
7.6 Auto CQ
This option is the same as Function Key 6 (F6).
7.7 Toggle DX Flag
LAN-LINK allows you to call either "CQ" or "CQ DX". If this flag
is set, all CQ calls will be to "CQ DX". If it is cleared, all CQ
calls will be plain CQ's.
7.8 Zap PBBS on Next Mail Beacon
This option causes LAN-LINK to Zap your local PBBS next time it
beacons with a list of calls for which it has Mail. You set this
option active when you want to upload a set of messages, or are
not sure if there are any messages waiting for you on the PBBS. A
typical situation is where there are a lot of NTS messages
stacked up in the PBBS.BBS file waiting to go. This parameter
will be reset when the connect goes through, so if the Zap
attempt failed, it will try again on the following Mail beacon.
This will not work in the Multi-user mode.
8.0 EDIT MENU
LAN-LINK contains an ASCII text editor suitable for files less
than 64k in size. It is based on Borland's Turbo Pascal Editor
Toolbox and the commands are compatible with Sidekick and
Wordstar. Each time you invoke the editor, LAN-LINK checks that
enough RAM exists to contain the file to be edited (64k per
file). If you do not have enough RAM, LAN-LINK will give you a
"Heap Error" message.
LAN-LINK 2.32 is supplied with an external editor. Run this from
DOS and you will be able to edit larger files. Make sure you put
the EDITOR.EXE file in the LAN-LINK subdirectory.
The Edit Menu is shown in Figure 8-1. Type in the single letter
to make your choice.
A summary of the commands used in the Editor is presented in
Figure 8-2. The ^ sign in front of a character identifies that
character as a "Control" character. To activate it, hold down the
Control key AND the character key. Some of the commands require
two keystrokes. Use ^P to embed a control character in the text.
For example, if you are creating a file containing commands to be
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 42
sent to the TNC, to enter a Control-C character into the file,
use the ^P^C sequence of keystrokes.
Figure 8-1 The Edit Menu
A LAN-LINK.OUT
B LAN-LINK.TXT
D LAN-LINK.DIR
E Pick dEmo File to Edit
F Any other File
G Incoming Message
K Answer Capture-to-disk file
L Leave Messages >> N4QQ
M Answer Incoming Mail
N Leave Note
O Pick OUT File to Edit
P Pick Ctdsk File to Edit
R Capture-to-disk file
S LAN-LINK.SYS
T Two Files
Z LAN-LINK.DMO
1,2 - 0 LAN-LINK.001 - 010
Figure 8-2 Summary of Editor Commands
F10 Switch Windows (if more than one window open)
Backspace Delete left char
Del Delete Char
Enter New line
Ins Toggle Insert mode
PgUp Move cursor up one page
PgDn Move cursor down one page
^A Move cursor left one word
^C Move cursor down one page
^D Move cursor right one character
^E Move cursor up one line
^F Move cursor right one word
^G Delete one character
^H Delete left one character
^I Tab
^L Find/replace next occurrence
^P Insert a control character into the text
^M New line
^N Insert line
^R Move cursor up one page
^S Move cursor left one character
^T Delete one word after cursor
^V Toggle insert mode
^W Scroll up
^X Move cursor down one line
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 43
^Y Delete line at cursor
^Z Scroll down
^K^B Mark beginning of block
^K^C Copy block to position of cursor
^K^D Save file and exit edit
^K^H Hide block marker
^K^K Mark end of block
^K^Q Abandon file and exit edit
^K^R Read file into screen
^K^T Mark single word as block
^K^V Move block to position of cursor
^K^W Write block to disk file
^K^Y Delete block
^K 1..9 Set marker 1 .. 9
^Q^A Find text and replace
^Q^B Move to beginning of block
^Q^C Move to end of file
^Q^D Move to right of line
^Q^E Move to top of window
^Q^F Find text
^Q^I Toggle autoindent mode
^Q^K Move to end of block
^Q^R Move to top of file
^Q^S Move to left of line
^Q^X Move to bottom of window
^Q^Y Delete to end of line
^Q 1..9 Jump to marker 1..9
The following options can be set in the Find/Find and Replace
(^Qf and ^Qa) operations.
# locates #th occurrence
G global replace
N replace without Y/N question
U ignore upper case/lower case
W match whole words only
While you are using the editor, LAN-LINK can't receive and
process characters from the TNC. All other features are inhibited
or locked out. Thus if someone connects to you, the TNC will know
but LAN-LINK will not. Be warned!!!
The Edit menu allows you to call up the various files for editing
as follows.
8.1 Edit Brag Tape
This option allows you to create and edit the Brag Tape File
(LAN-LINK.TXT).
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 44
8.2 Edit Call Directory File
This option allows you to create and edit the Call Directory File
(LAN-LINK.DIR).
8.3 Edit Any Other File
This option allows you to create and edit any other file.
8.4 Answer Capture-to-disk (Ctdsk) File (Split Screen)
This option allows you to edit the capture-to-disk file and reply
to incoming bulletins/messages in a split screen mode. The
contents of the incoming bulletins and messages will be displayed
in the top window, and the reply file in the lower window.
The reply file is assumed to be named according to the Zap
convention (*.BBS file). You will have to set up the replies/-
outgoing messages as if you were typing them by hand.
You put "SP Call @ PBBS" in the first line, then the "Subject of
the message" in the next. Enter the message, and end it with
":EOF:" , "/ex" or "/EX" as the first word on a separate line.
For example, a message to me could take the form shown below.
SP G3ZCZ@N4QQ
Test
This is a test
73 your name
/ex
8.5 Answer Incoming Messages (Split Screen)
This option allows you to answer incoming messages in a split
screen mode. The contents of the incoming messages will be
displayed in the top window, and the reply file in the lower
window. The reply file is assumed to be named according to the
Zap convention (LOCAL-BBS.BBS file). Reply messages are set up as
described in Section 8.4.
Use Function key 10 (F10) to switch windows. At this time you
cannot transfer text between windows.
8.6 Leave Note for Someone
In all modes you can leave a brief note (message) for another
station. When you invoke this option, you will be prompted for
the call of the station that you want to leave a note for. As you
enter the text it is stored on the disk in the usual format.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 45
After you have left the note, if you are in the Packet Communi-
cations Mode, press Function Key 8 (F8) or Alt-D to load the
callsign of the recipient into the beacon.
When you leave a note, leave it for the root call of the
connectee, for example to leave a note for W3/G3ZCZ or G3ZCZ/W3
leave it for G3ZCZ, similarly to leave a note for WB8WKA-1 leave
it for WB8WKA. LAN-LINK is smart enough to extract the root call
from any callsign it links/connects with.
8.7 Edit Capture-to-Disk file
This option allows you to edit the Capture-to-Disk file as long
as it is smaller than 64k.
8.8 Edit Two Files (Split Screen)
This option allows you to create and edit any two files. Use
Function Key 10 (F10) to switch windows. At this time you cannot
transfer text between windows.
8.9 Edit Configuration file
This option allows you to edit the Configuration File (LAN-
LINK.SYS).
8.10 Edit LAN-LINK.001 through LAN-LINK.010 Files
This option allows you to create and edit the 10 files (LAN-
LINK.001 to LAN-LINK.010). Use the suffix number to access the
respective LAN-LINK.* file, use the number 0 to access the LAN-
LINK.010 file. If the Mode File Flag is set (see 10.14), the file
names will change according to the modes.
8.11 Pick Capture-to-disk File to Edit
This option presents you with a directory window containing a
list of capture-to-disk files (YYMMDD.RUN). Move the cursor down
to the desired file and touch the "Enter" key. If you don't want
to edit any of them, then move the cursor down to a blank line.
If you have more files than one screen full, use the Pgdn (Page
Down) key to show the next screen full.
8.12 Pick Message File to Edit
This option presents you with a directory window containing a
list of message files (*.OUT). Move the cursor down to the
desired message file and touch the "Enter" key. If you don't want
to edit any of them, then move the cursor down to a blank line.
If you have more files than one screen full, use the Pgdn (Page
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 46
Down) key to show the next screen full.
8.13 Leave Messages on your local PBBS
This option allows you to edit your LOCAL-BBS.BBS file in a
single window.
8.14 Edit Incoming Message
This option allows you to edit your incoming message file in a
single window.
8.15 Edit LAN-LINK.OUT File
This option allows you to edit the LAN-LINK.OUT file.
8.16 Edit LAN-LINK.DMO File
This option allows you to edit the Demo or Test file. This is a
file you can read into LAN-LINK and LAN-LINK treats it as if the
data came from the TNC. Use this option to test features and
custom settings.
8.17 Pick dEmo File to Edit
This option allows you to pick a demo file to edit.
9.0 EVENT/CLOCK MENU
LAN-LINK contains some time dependent features which allow you to
schedule events. These features are controlled from this
Event/Clock Menu shown in Figure 9. Type in the single letter to
make your choice.
Figure 9 Event/Clock Menu
A Set Alarm
C Connect ?
D Display Event
P Periodic Connect ?
R Turn Robot ON/OFF
S Turn ConteSt ON/OFF
T Turn Time Display ON/OFF
X Cancel Event
Z Zap PBBS
To set a scheduled event, first select the event, then enter the
time. You may set the event to occur once a day, or once an hour.
If you wish the event to occur once an hour, enter an hour value
greater than 23 when asked to enter the hour. Each time the event
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 47
occurs, the feature will be cleared.
9.1 Set Alarm
This option allows you to set an alarm clock.
9.2 Connect
This option allows you to set LAN-LINK to issue a call or connect
request at some later time.
9.3 Display Event
This option allows you to display the scheduled event.
9.4 Periodic Event
This option allows you to set a periodic connect request or call
event. You can set the start time, the end time and the time
interval between the connect/call attempts. The first connect
that goes through will clear the event scheduler.
9.5 Turn Robot ON/OFF
This option allows you to turn the AMTOR/Packet Robot on or off
at a fixed time.
9.6 Turn Contest ON/OFF
This option allows you to turn the AMTOR/Packet Automatic
Contester on or off at a fixed time. You will be prompted for the
time, a starting QSO number (in case you a restarting the
contest) and the Contest Text (in case you wish to change it).
9.7 Turn Time Display ON/OFF
This option allows you to turn the clock display on or off.
9.8 Cancel Event
This option allows you to cancel a scheduled event.
9.9 Zap PBBS
This option allows you to schedule a PBBS Zap at a predetermined
time (like in the middle of the night). You may for example set
it to attempt to connect to a PBBS at a fixed time or hourly at
any desired minute after the hour. Should the connect be made,
the event scheduler will be cleared and no further connect
attempts will be made.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 48
10.0 FILES MENU
The Files Menu is shown in Figure 10. Type in the single letter
to make your choice.
Figure 10 The Files Menu
B Send Brag Tape
C View Color File
D File Directory
E Erase File
F priNt File
M Turn Mode Files ON/OFF
N priNt Ctdsk File
P Pick Ctdsk File to View
R Rename File
S Send File
T Send/Talk File
U send Uppercase File
V View File
Y View Capture-to-disk File
X Turn eXpand Files OFF
Z View Messages
10.1 Send Brag Tape
This command allows you to transmit a standard text file
historically known as a "Brag Tape". The default name of the brag
tape file is LAN-LINK.TXT, and it should be created with a word
processor in the non-document mode, or with LAN-LINK's editor.
During the file transfer, the outgoing text will appear in the
Outwindow. If the text is long enough and fills the TNC buffer,
you will see it stop, and then continue when the TNC is ready to
accept more text. LAN-LINK uses hardware flow control not
software (^S/^Q).
When you transmit a file you are returned to the receive mode
after the file is sent except in the Packet Communications Mode.
In the Packet Communications mode, when the file has been loaded
into the TNC the computer will add the ^Z character to the
outgoing text to signal to the recipient that the file transmis-
sion is over.
The computer will signal you (using the bell character) when the
file has been loaded into the TNC. That is not the same as the
time that the TNC has transmitted the file, because the TNC
contains a character buffer. LAN-LINK dumps the file into the TNC
at the baud rate used between the PC and the TNC. The TNC, then
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 49
transmits the file at the radio link data rate. Flow control is
used to regulate the passage of data between the various buffers
in the link.
10.2 File Directory
This command shows you the directory of the disk drive.
10.3 Erase File
This command allows you to erase or delete a file.
10.4 Pick Capture-to-disk (Ctdsk) file to View
This command allows you to view a *.RUN file. When you exercise
this command you will be presented with a list of capture-to-disk
files (YYMMDD.RUN). Move the cursor down to the one you want to
view and touch the "Enter" key to select it. Use this option, if
you must, on long files. On files containing less than 64k
characters, use the Edit Menu.
10.5 Rename File
This command allows you to rename a file. You could for example
rename a document file to a "CALLSIGN.OUT" file so that someone
will receive it automatically next time they connect.
10.6 Send File
This option lets you transmit an ASCII file. In the non packet
modes, it will turn the transmitter off after sending the file.
In the packet mode it will send a ^Z character when the file is
complete.
10.7 Send/Talk File
This option lets you transmit an ASCII file. In the non packet
modes, it will leave the transmitter on after sending the file.
10.8 Send Uppercase File
This option lets you transmit an ASCII file and converts each
line of text in the file to UPPERCASE before transmitting it. The
file itself is not changed. In the non packet modes, it will turn
the transmitter off after sending the file.
10.9 View File
This option lets you view the contents of a file. Use it if you
must on long files. On files containing less than 64k characters,
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 50
use the Edit Menu.
10.10 View Capture-to-disk (Ctdsk) File
This option lets you scroll forward through, or view, the
contents of the capture-to-disk file (YYMMDD.RUN) which you
specify by name. Use it if you must, on long files. On files
containing less than 64k characters, use the Edit Menu.
10.11 View Incoming Message File
This option lets you view the contents the Incoming message file
(yourcall.OUT). Use it if you must, on long files. On files
containing less than 64k characters, use the Edit Menu.
10.12 Print File
This option lets you print the contents of a text file.
10.13 View Color File
This option allows you to view an ANSI color file in glorious
color. If you use the regular edit or file view options, you will
see the ANSI color control characters inside the file. Use this
option to check on your color editing.
10.14 Turn Mode Files ON/OFF
This option lets you change the state of the Mode File Flag. If
this flag is set, LAN-LINK will change the name of the LAN-
LINK.001 to LAN-LINK.010 when you change modes. The name will
change to the mode followed by a number, i.e. BAUDOT.001 to
BAUDOT.002, or AMTOR.001 to AMTOR.002. This feature allows you to
use different files in different modes and still use the same Alt
key combination to transmit them. Thus, you can if you wish, set
up a Pactor file with all 128 characters, and an AMTOR file with
the AMTOR character set as MODE.002, (where MODE is the
communications mode) and transmit each using Alt-F2. If the Mode
File Flag is not set, then the file names never change.
10.15 Turn eXpand Files ON/OFF
This option lets you change the state of the eXpand File Flag. If
this flag is set, LAN-LINK will change the macro string beginning
with the # sign, to the equivalent text.
11.0 HELP WITH FUNCTION KEYS
This Main menu option will activate the HELP display which
presents you with a (very) brief reminder summary of the function
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 51
and hot keys. This window will remain on display until a
character is typed at the keyboard.
12.0 JUMP TO DOS SHELL
This Main menu option allows you to enter a DOS shell. If you do
not restore the system to the directory which contains LAN-LINK
before you EXIT from the shell, LAN-LINK will do so for you.
You may use the DOS shell while in QSO when you have loaded the
computer/TNC output buffers and output will continue to flow.
To exit from the DOS shell back to LAN-LINK, enter the command
"EXIT". LAN-LINK will automatically return you to the correct
sub-directory.
13.0 LAN-LINK MENU
The LAN-LINK menu provides different options depending on whether
you are connected to another station or not. Figure 13.1 shows
options that are available when connected and the PAcketCluster
flag is not set. Figure 13.2 shows the menu when not connected.
In each case, type in the single letter to make your choice.
Each of the features (except the :QYU:) may also be performed
manually by typing the full sequence of Network Control Language
character strings.
13.1 :QBU: External Protocol Command
This is a Sequence for external operations. It requires that the
batch file "QBU-TX.BAT" be present in the transmitting
(initiating) station, and the batch file "QBU-RX.BAT" be present
in the receiving station. When the QBU sequence is executed the
following occurs:-
Figure 13.1 LAN-LINK Menu When Connected
9 Demo Mode
B :QBU: Protocol
D :QZD: Binary File
G :QIC: Page Operator
H :QMH: Activity
M :QBM: ASCII File
P :QSP: Message
Q :QDB: ASCII File
R :QTR: Ask for Time
S :QSM: Message
T :QTA: Message
U :QRU: Messages
Z :QZU: Binary File
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 52
Figure 13.2 LAN-LINK Menu When Not Connected
9 Demo Mode
W Who is "ON-LINE"
The transmitting station sends a :QBU: The receiving station
sends a :QRV: and the amount of memory left on disk, enters the
transparent mode, jumps to dos and executes the batch file "QBU-
RX.BAT".
Upon receipt of the :QRV:, the transmitting station then puts the
TNC in the transparent mode and jumps to Dos and executes the
batch file "QBU-TX.BAT". The batch file should exit and return to
LAN-LINK. LAN-LINK then exits the transparent mode.
When the receiving station batch file finishes and returns to
LAN-LINK. LAN-LINK then exits the transparent mode and transmits
a :QSL: if the DOS Error level was 0 and a :QNO: error if it
wasn't. At this time both stations are back in the converse mode.
You may use this technique for transmitting pure binary files
using external (to LAN-LINK) protocols). You may change the
default names of the batch files in the LAN- LINK.SYS
configuration file.
13.2 :QBM: ASCII File
You use this option to download an ASCII file from another LAN-
LINK station. It is the same as manually typing ":QBM: FILENAME".
13.3 :QDB: ASCII File
You use this option to upload an ASCII file to another LAN- LINK
station. It is the same as manually typing ":QDB: FILENAME".
Using this option saves you typing the file name twice.
13.4 :QIC: Page Operator
This command allows you to page the operator at the other LAN-
LINK 2.1+ station. The sequence is:- you send :QIC: to another
LAN-LINK 2.1 station. Use the LAN-LINK Menu or type it by hand.
Upon receipt, LAN-LINK begins to page the operator if the sound
flag is on. At that time it sends you a :QRX: followed by a
number, i.e. ':QRX: 30'. The number is the number of seconds it
will page the operator. At the end of the paging sequence it will
send the prompt i.e. 'G3ZCZ>'. If the sound is inhibited it will
send ':QRX: QRT' to signal that it is in a silent configuration.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 53
13.5 :QMH: Monitor Heard
This command causes your copy of LAN-LINK to issue the :QMH:
command. When the other station's copy of LAN-LINK receives a
:QMH: command, it drops back to the TNC Command Mode and issues a
"MH" command to the TNC (except to a TNC1 which does not support
it). It stores the list received in a temporary buffer, and then
returns to the Converse Mode and transmits the list back to you.
13.6 :QRA: Who is "ON-LINE"
You use this option (when unconnected and monitoring the traffic
on a channel) to see who is "ON-LINE" on the LAN. It is the same
as going manually into the Converse Mode and transmitting an
unconnected packet containing the character string :QRA:. You may
also use the Alt-W function key to transmit the same sequence.
13.7 :QRU: Messages
The NC/L QRU command allows you to upload a number of messages to
the other station. You use it when you have messages pending on
your system and want to pass them to a third computer for storage
in the LAN, while you take your computer off-line.
You use this option to begin the upload sequence to transfer
messages for a number of stations to another LAN-LINK station. It
is the same as manually typing :QRU:.
You can only use this option with a station which you have
previously designated as a store and forward mail box, for
specific stations. You must also have set up a CALLSIGN.MBX file
for that station.
When the upload sequence is over, the computer sending the
messages will transmit the NC/L command word :QJG: to signal that
the sequence is complete. Should you receive it before you get
any messages, then there weren't any pending.
If you want to upload messages to another LAN-LINK system,
connect to it and type the sequence :QRU: followed by the "Enter"
character. That system will then respond to you as if the
operator there had initiated a QRU command.
13.8 :QSM: Message
You use this option to request a repeat of a message. It is the
same as manually typing ":QSM:".
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 54
13.9 :QSP: Message
You use this option to store a message on another LAN-LINK
station. It is the same as manually typing ":QSP: CALLSIGN".
LAN-LINK contains store and forward routines for messages in a
Local Area Network (LAN).
When connected to another LAN-LINK station, you may use the NC/L
:QSP: command to leave a message at that station. This QSP
command automates that feature for you. It lets you just enter
the callsign of the station you wish to leave a message for. It
will then send the text sequence :QSP: <callsign>. The other LAN-
LINK HOST station will either reply :QNO: followed by a number or
:QRV: <callsign>. The "QNO" message means that the other computer
cannot accept the message, the "QRV" message means that it is
waiting for you to send it.
If you get the :QRV: reply, go ahead and type the message, or
send the text file containing the message. If you type the
message, use a Control-Z (^Z) character and carriage return to
terminate the message. (In AMTOR, LAN-LINK will translate the ^Z
to :EOF: +? to terminate the message). You will then receive
either a :QSL: from the other station meaning that the message is
accepted, or a :QNO: followed by a message that something went
wrong and the message was not stored.
13.10 :QTA: Messages
If you have a bad path and your messages are not automatically
deleted by the other station after they have been sent to you,
you use this option to delete your message. It is the same as
manually typing ":QTA:".
13.11 :QTR: Ask for Time
This command allows you to get the date-time-text string from the
other LAN-LINK 2.1+ station. Don't confuse it with :QRT:.
13.12 :QZD: Binary Files
This command uses the external batch files to download a Binary
file from another LAN-LINK Station using the Zmodem Protocol. If
you attempt to download a file which exists in your computer,
LAN-LINK will use ZModem's "restore after interrupt" capability
to pick up the transfer at the point when (it assumes) the
transfer was interrupted. You must configure all four QZ*.BAT
files before trying to :QZD: as described in Section 24 (Install
takes care of the configuration in most instances).
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 55
13.13 :QZU: Binary Files
This command uses the external batch files to Upload a Binary
file to another LAN-LINK Station, making use of the Zmodem
Protocol. LAN-LINK will not let you upload a file to the other
system, if a file with that name already exists on the system.
This stops you overwriting existing files. If the link drops out
while you are uplinking a file, and you wish to try again later,
rename the file you are sending, then reconnect and try again.
Don't forget to :QSP: the other station and tell the operator
what happened. You must configure all four QZ*.BAT files before
trying to :QZU: as described in Section 24.
13.14 Demo Mode
Use this option to enter the demo mode, and simulate incoming
lines of text from a disk file.
13.5 Set Single/Dual PK-900/DSP 2232 In Windows
This option in only active for the PK-900 and DSP 2232. It allows
you to separate the incoming text from the two radio ports into
two windows. When operating hf/vhf the hf window is usually the
middle incoming window.
14.0 LOG MENU
LAN-LINK allows you to have up to 3 logbooks on-line. One is
designated as the HF logbook, the second is the VHF logbook, and
the last one is known as the Secondary Logbook. They can be
different or the same.
LAN-LINK performs automatic log book entries for Packet, Pactor
and AMTOR Beacon mode Connects, and semi-automatic log book
entries for other modes. The Log files are in dBASE 3 format and
can be processed by the DBASE Log book Package in PC-HAM for
indexed listings, tracking of DXCC and other AWARDS, etc. This is
ideal for special event stations and DX-peditions, for the whole
QSL process and further statistical analyses of their operation.
The structure of the logbook files are as shown in Table 14.
The size of the COMMENTS field is a compromise. Each field is a
fixed size so that each log entry takes up a minimum of 62
characters worth of space on the disk even if all the character
space is unused. You may change the size of the field if you
wish, but to do that you will have to use dBASE. Note also, that
if you do make the comments field longer, the display will be
screwed up.
For the logging feature to work, the logbook files must be
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 56
present on the disk.
Table 14 Structure of the Logbook Database File
Field Field Name Type Length
1 DATE Character 8
2 TIME Character 4
3 BAND Character 3
4 CALL Character 10
5 RX Character 3
6 TX Character 3
7 MODE Character 4
8 POWER Character 4
9 QSLSENT Character 1
10 QSLRX Character 1
11 COMMENTS Character 20
When an AMTOR beacon mode, G-TOR, Pactor, or packet connect
occurs, the connect is automatically logged (if the automatic
logging feature is enabled). In the Packet Mode, the connect path
is placed in the comments section of the logbook entry. In the
non packet modes, the log data entry is set up for you with
default 599 values for the reports exchanged.
When you bring up the Logbook you will be shown the last screen
or page of log entries. The last entry will be highlighted. At
this time a number of function keys can be used, or you may
depress the "Escape" key to bring up the Main Log Menu. When you
bring up the Main Log Menu, it provides the choices shown in
Figure 14.1. Type in the single letter to make your choice.
14.1 Append From Another LAN-LINK Log
This option lets you append entries from another LAN-LINK
logbook. Use it after a contest, to merge the contest log into
the main logbook.
14.2 Scan Log by Band
This option lets you scan the logbook file and display QSOs made
on a particular band.
14.3 Change Logbook File
This option lets you temporarily change the logbook file. If you
want to change it permanently, change it in the LAN- LINK.SYS
file. When you enter the new name, LAN-LINK will assume that it
is a filetype DBF. For example, if you have different logbooks
for different operations on-line, such as 4X.DBF or W8.DBF, you
only need answer "4X" in response to the question, to change to
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 57
the 4X.DBF logbook. In accordance with the dBASE convention, you
cannot use any filetype other than DBF.
Figure 14.1 The Log Menu
A Append from Another LAN-LINK Log
B Scan Log by Band
C Change Log
D Delete Logbook
F Find date
G Purge Log
H Help Function Keys
I Import From G3ZCZ's Contest Log
J Jump to an Entry
K PicK Log
L pack Logbook
M Scan Log by Mode
N Create New Blank Log
P Print Log
R Re-index Logbook
T Sort on Date + Time
U Turn Update Disk OFF
Z fuZzy scan
2 Turn Secondary Search OFF
14.4 Delete Logbook File
This option lets you delete both the logbook (.DBF) and its
associated index file (.NDX).
14.5 Find Date
This option lets you locate and move the highlight to entries for
a particular date. If no entries are found for the desired date,
the first entry after that date will be highlighted. You can also
scan for parts of a date, such as "90/01", for the first entry in
January 1990.
14.6 Purge Log
This command allows you to purge one callsign from the log. Use
it to delete the callsign of your local PBBS if the logbook file
gets too big.
14.7 Help Function Keys
This option brings up a menu listing the log mode function keys.
14.8 Import From G3ZCZ's Contest Log
This option lets you import logs from earlier releases of LAN-
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 58
LINK (up to and including Version 1.56). It can also be used to
import a log generated by the Contest Program in PC-HAM.
14.9 Jump to an Entry
This option lets you jump to an entry by its record number. This
is the number displayed in the first column.
14.10 Pick a Log file
This command allows you to pick a *.DBF file. When you exercise
this command you will be presented with a list of log files
(*.DBF). Move the cursor down to the one you want to use and
touch the "Enter" key to select it.
14.11 Pack a Logbook
This function key allows you to pack the logbook files. All
entries marked for deletion will really be deleted at this time.
14.12 Scan Log by Mode
This option lets you scan the logbook file and display QSOs made
using a particular mode.
14.13 Create a New Logbook
This command allows you to create a blank logbook (*.DBF) file.
14.14 Print Log
This command prints the contents of the logbook file in a
formatted manner to the printer.
14.15 Re-index a Logbook
This command allows you to index logbooks that you have ported
over from other DBASE formats, or to re-index logbooks that have
had their index files damaged in some manner.
14.16 Sort on Date + Time
This command allows to you create a new logbook from the current
one with the entries is sequential order sorted on date and time.
You use this option after entering old QSOs manually. Make sure
there is space on the disk for a temporary logbook before evoking
this operation.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 59
14.17 Turn Update Disk ON/OFF
If this parameter is set ON, LAN-LINK will close the logbook and
re-open it after every entry. If the parameter is set OFF, LAN-
LINK saves a few entries in memory and only writes them to disk
when the buffer fills, or the logbook is closed. Setting the
parameter guarantees you will not lose any entries if the power
fails, at the expense of a slightly slower logging operation.
14.18 Fuzzy Scan
This option allows you to scan the callsign or the comment field
(your choice) for a character string. For example you could scan
the comments field for all entries with the word "Joe". You could
scan the callsigns for all calls with the suffix of "ZCZ".
14.19 Turn Secondary Search ON/OFF
This option allows you to turn the secondary search mode on and
off. If it is on, and if the secondary logbook exists, every time
you command a search of the logbook to find a prefix or callsign,
LAN-LINK will also search the secondary log. Use this feature if
you have more than one log, as a result of operating from more
than one location or for any other reason.
14.20 Log Menu Function Keys
The Function Keys shown in Figure 14.2 are active in the Log
book. The operation of each function key is described below.
Figure 14.2 Function Keys Active in Log book
A Append Entry
E Edit Log Entry
H Scan for Log Entry
S Scan for Call
U Toggle Delete Mark
X eXit Log Menu
Ins Toggle Insert Mode
End Show Last Page
Home Show First Page
PgUp Page Up
PgDn Page Down
Up One Entry
Down One Entry
14.20.1 Alt-A Append Entry
This function key allows you to manually append an entry to the
log. You can also use this command to enter the odd SSB contact
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 60
into the logbook file. If you do, use the characters "SSB" or
"FM" for those voice modes to remain compatible with the rest of
the DBASE logbook package.
When appending or editing an entry, LAN-LINK will automatically
enter the date, time, callsign of the other station, band, mode
and QSL information in upper case.
The comments field in the LAN-LINK logbook file is restricted to
a maximum of 20 characters. If you try and enter more than 20,
the surplus will be ignored.
14.20.2 Alt-E Edit Log Entry
This function key allows you to edit the highlighted entry. Move
the cursor with the arrow keys, and end the edit process by
depressing the "Escape" key.
You may use the "QSL" entry to tag the fact that you have written
out or received a QSL card.
14.20.3 Alt-H Scan Log by Call
This function key allows you to scan the logbook by callsign
prefix for the callsign in the highlighted entry in the logbook.
This command displays the contents of the logbook file in a
formatted manner on the screen. It requests the callsign of the
log entry to be displayed. If you want to see entries for
particular callsigns or parts of a callsign, enter those
callsigns or the front parts of the callsign. Valid entries are
G, G3, G3Z etc. If you want to see every entry in the log, don't
use this command, use the Page Up and Page Down keys from the
Main Log menu.
14.20.4 Alt-S Scan Log by Call
This function key allows you to scan the logbook by callsign
prefix for the callsign entered with the Alt-C or Alt-E keys.
This command displays the contents of the logbook file in a
formatted manner on the screen. It requests the callsign of the
log entry to be displayed. If you want to see entries for
particular callsigns or parts of a callsign, enter those
callsigns or the front parts of the callsign. Valid entries are
G, G3, G3Z etc. If you want to see every entry in the log, don't
use this command, use the Page Up and Page Down keys from the
Main Log menu.
14.20.5 Alt-U Toggle Delete Mark
This function key allows you to mark an entry for deletion, or
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 61
unmark it in case you change your mind. Entries marked for
deletion will be flagged by an "*" character next to the record
number.
14.20.6 Alt-X eXit Log
This function key lets you exit from the Logbook.
14.20.7 Ins Toggle Insert Mode
This function key allows you to turn the insert mode ON and OFF
for the edit/append functions.
14.20.8 End Show Last Page
This function key moves you to the last callsign on the last page
of the logbook.
14.20.9 Home Show First Page
This function key moves you to the first callsign on the first
page of the logbook.
14.20.10 PgUp Move Up One Page
This function key moves the display up one page of the logbook.
14.20.11 PgDn Move Down One Page
This function key moves the display down one page of the logbook.
14.20.12 Up Arrow Move Up One Entry
This function key moves the highlight up one entry in the
logbook.
14.20.13 Down Arrow Move Down One Entry
This function key moves the highlight down one entry in the
logbook.
15.0 MESSAGE MENU
The Message Menu is shown in Figure 15. Type the single letter to
make your choice.
Figure 15 The Message Menu
B PBBS Command Files
C Current Messages
L Leave Note
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 62
N Print Message
O Old Messages
T Time Tag
V View Messages
15.1 PBBS Command Files
This option shows you a list of the PBBS command files on the
default directory. In other words, all files with the file
extension of ".BBS".
15.2 Current Messages
This option shows you a list of the outgoing messages that have
not been sent. In other words, all files with the file extension
of ".OUT".
15.3 View Message
This feature allows you to view messages in the computer. After
depressing the key you will be prompted for INcoming or OUTgoing
(I/O) messages. If you request "I" (Incoming) messages you will
see the messages addressed to your callsign. If you request "O"
(for OUTgoing) you will be presented with a directory window
containing a list of messages. Move the cursor down to the
desired message, and touch the "Enter" key. If you don't want to
view any of them, then move the cursor down to a blank line. If
you have more messages than one screen full, use the Pgdn (Page
Down) key to show the next screen full.
15.4 Leave Note
This feature allows you to leave a note for another station on
the LAN in your system. It works using the editor in the manner
described in Section 8.
15.5 Old Messages
This feature shows you a list of the messages that have been
sent. In other words, all files with the file extension of
".OLD".
15.6 Time Tag
This option is used to place a date time header on a message file
previously prepared by a word processor. The name of the file
must be in the format "CALLSIGN.OUT" (i.e. G3ZCZ.OUT). It
requests the callsign of the message file. It then opens a new
file, writes the header to the new file and copies the contents
of the original "*.OUT" file to the new one. When all is done,
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 63
the original filename is changed to "*.BAK" and the new one
becomes "*.OUT".
16.0 TNC MENU
The TNC Menu depends on the TNC. For example the MFJ1278 provides
the choices are shown in Figure 16-1. The PK-232 TNC menu is
similar as shown in Figure 16-2. The actual menu you see also
depends on the mode. In the non packet modes, the non packet
options will be locked out. For example, in the PK-232 Baudot
mode, the menu will appear as shown in Figure 16-3.
The DSP-2232 and PK-900 support simultaneous dual port operation.
LAN-LINK provides for support of this feature, so the TNC Menu
for those TNCs has additional options as shown in Figure 16-4.
Figure 16-1 MFJ1278 TNC Menu
D Set MFJ1278 Date/Time
E Disable MFJ1278 Port
F Flush MFJ1278 Buffer
I Initialize MFJ1278
M calls Monitored List
S Show Connect Status
T Change cText
X Activate MFJ1278 Mailbox
Y Deactivate MFJ1278 Mailbox
Figure 16-2 The PK-232 TNC Menu
D Set PK232 Date/Time
E Disable PK232 Port
F Flush PK232 Buffer
I Initialize PK232
M calls Monitored List
S Show Connect Status
T Change cText
X Activate PK232 Mailbox
Y Deactivate PK232 Mailbox
Figure 16-3 The PK-232 TNC Menu in BAUDOT
D Set PK232 Date/Time
E Disable PK232 Port
F Flush PK232 Buffer
I Initialize PK232
Figure 16-4 The PK-900 TNC Menu in Packet
D Set PK900 Date/Time
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 64
E Disable PK900 Port
F Flush PK900 Buffer
I Initialize PK900
M calls Monitored List
N PK900 Modem Menu
S Show Connect Status
T Change cText
X Turn PK900 Mailbox ON
Y Turn PK900 Mailbox OFF
1 Select Radio Port 1
2 Select Radio Port 2
3 Disable Radio Port 1
4 Disable Radio Port 2
5 Enable Radio Port 1
6 Enable Radio Port 2
7 Show ## Radio Port
Whichever menu is displayed, type in the single letter to make
your choice.
16.1 Set TNC Date/Time
This feature puts the TNC into the Command Mode and loads the
date into it from the computer time of day clock. This command
does not work on the TNC1.
16.2 Flush TNC Buffer
This option is used to flush LAN-LINK's incoming or outgoing text
buffer and that of the PK-232, PK-900 or DSP 2232. When used with
other TNCs it will only flush contents (if any) of the buffers in
the PC. If you flush the incoming buffer, you will only flush the
buffer in the PC. Any characters still in the TNC buffer will
still come through. If that happens, bring up the function but
wait a while before activating it.
16.3 Initialize TNC
This feature sets up the defaults for the TNC from the file LAN-
LINK.SYS. If you have put batteries in the TNC, you should
normally only have to run this command when you first power up
the TNC or change the batteries. However, the batteries must be
removed initially since they are there to retain the default
settings of the TNC (particularly the PK-232). Once the
initialization is complete, you can replace the batteries but
leave the TNC on since the battery provides power to the RAMs
after the TNC power is turned off.
The function will also set the date and time within the TNC from
the PC computer clock, and, when it has loaded the configuration
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 65
file, may prompt you to set the TNC Terminal mode. If you are
using a TNC1 or a TNC2, it will not prompt you because it assumes
that they only operate on VHF packet. If you are using a KPC-2,
you may select "H" or "V", and of course, if you have a PK-232,
you may choose any of the options.
16.4 Show Calls Monitored List
This option performs the same operation as Function Key 5 (F5).
16.5 Show Connect Status
When you are in the Packet Communications Mode, this command lets
you see the state of the connection. It will show you if there
are any unacknowledged packets en route to the other station. If
you have been sending text, it is advisable to use this command
before you disconnect, to ensure that all the data has been
received and acknowledged by the other party. You may use this
command in either the TNC Command or the TNC Converse Mode.
In a multi-connect situation, it will show you the status on all
the I/O channels.
You may also use this command to reset the status window display
after a relink or any other event which was not reflected in the
status window.
16.6 Change CTEXT
This feature allows you to change the message that will be
received by another packet station when it connects to you. Refer
to the CTEXT command in the TNC manual.
16.7 Activate TNC Mailbox
The mailbox in your TNC provides a convenient way for people to
leave you a message when your PC is switched off or is in use for
something other than packet radio. If you do choose to make use
of the personal PBBS in the mailbox, make sure that you have a
battery in the TNC. You will have to interrogate the mailbox in
the command mode to view any messages. Type the commands listed
in your TNC manual.
This menu option allows you to activate the personal mailbox
built into your TNC to read any messages stored in it, or, before
shutting down, if you have not set the shut down mode to 5.
To save your local full service PBBS SYSOP some hassles, it is
strongly recommended that you let LAN-LINK do your outgoing and
incoming message and bulletin store and forwarding. Use the "L"
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 66
option in the Edit menu to enter any messages off-line, the "M"
and "K" options in the Edit menu to answer any incoming messages
or comment on any bulletins. Once the messages are written into
the LOCALPBBS.BBS file, let the PBBS Zap take care of
transferring the messages to the PBBS.
16.8 Deactivate TNC Mailbox
This option allows you to deactivate the personal mailbox built
into your TNC.
16.9 TNC Modem Menu
This option applies to the PK-900 and DSP 2232. It interrogates
the TNC and displays list of the modems in the TNC.
16.10 Select Radio Port 1
This option applies to the PK-900 and DSP 2232. It sets outgoing
text to Radio Port 1.
16.11 Select Radio Port 2
This option applies to the PK-900 and DSP 2232. It sets outgoing
text to Radio Port 2.
16.12 Disable Radio Port 1
This option applies to the PK-900 and DSP 2232. It disables all
input from Radio Port 1.
16.13 Disable Radio Port 2
This option applies to the PK-900 and DSP 2232. It disables all
input from Radio Port 2.
16.14 Enable Radio Port 1
This option applies to the PK-900 and DSP 2232. It disables all
input from Radio Port 1.
16.16 Enable Radio Port 2
This option applies to the PK-900 and DSP 2232. It disables all
input from Radio Port 1. You might want to use it to temporarily
disable the vhf port when receiving an ANSI color picture on the
HF port.
16.17 Show ## Radio Port
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 67
This option applies to the PK-900 and DSP 2232. It displays the
current TNC connect and radio port status.
17.0 AMSAT-OSCAR MENU
This menu allows you to configure the KAM, MFJ1278, or the PK-232
to copy signals from AMSAT-OSCAR Spacecraft telemetry beacons
depending on the TNC. The following options are available.
D Full Duplex ON/OFF
S SAREX Menu
Type in the single letter to make your choice.
17.1 Full Duplex ON/OFF
This option allows you to turn the FULLDUPLEX parameter in the
TNC ON and OFF. Set it to OFF (default) when working a station
simplex (same uplink and downlink frequencies) i.e. MIR. Set
FULLDUPLEX to ON when working a station duplex (different uplink
and downlink frequencies) i.e. SAREX and Fuji-OSCAR 20.
17.2 SAREX MENU
This menu shown in Figure 17-1, is only active in the Packet
Communications Mode. It is designed for use with the Shuttle
Amateur Radio Experiment (SAREX), MIR, and the packet radio
Microsats, or any terrestrial station you want to connect with as
soon as they appear on frequency. Apart from the Attack Mode, it
can also be used as a diagnostic LAN tool for monitoring LAN
traffic.
Figure 17-1 The SAREX Menu
A Set Attack Mode ON
C Set SAREX Call
D Edit SAREX Capture File
L Turn SAREX Capture ON
M set Attack Mode Connect/CQ
Z Turn Zap MIR-1 ON
0 Multiple User Connects
17.2.1 Attack Mode ON/OFF
If the Attack Mode is set, this option will cause LAN-LINK to
issue a connect request to the SAREX Call whenever a packet sent
to or from it is heard. The mode, is cleared when the connect is
made (and does not retry out) or when the "A" option is selected
a second time, or when the Alert Call is cleared. If this mode is
enabled, the Alert/SAREX Call prefix shown in the Status Window
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 68
will indicate accordingly.
A happy face will be displayed next to the ">" before the call
once the connect has been achieved.
Be careful using this feature, as it has the potential to cause a
great deal of QRM. It can also be cleared by another station
connecting to you and telling you to ":QRT:".
In the SAREX configuration you are listening on one channel while
transmitting on an other. If this feature is used on a simplex
channel (everyone transmits and listens on the same channel)
aimed at a DX-pedition or the MIR space station, there is a
potential lockout mode, in which any one station sending a
connect request to the desired/SAREX call will trigger the other
ones on frequency who will in turn trigger the first. If this
pile up situation occurs, I hope the DX-station will QSY and
leave the automatic stations to do their thing. IN any event, if
you use this feature and cause QRM, anyone can connect to you
with the callsign of the DX station (as a pirate) and shut you
down. You will then not get the coveted DX QSL.
17.2.2 Change SAREX Call
This option lets you temporarily change the SAREX call.
17.2.3 SAREX Packets Capture to Disk ON/OFF
This option allows you to configure LAN-LINK to capture to disk
any packets addressed to or from the SAREX callsign. A "[S]" will
be displayed in the status window when this option is active. The
capture to disk file is opened by a packet header containing the
SAREX call, and closed by another packet header not containing
the call. When the file is open, the "[S]" will blink. Packet
headers are considered to be lines with a ">" character in them.
LAN-LINK thus considers both of the lines below as packet
headers.
N4QQ*>G3ZCZ
N4QQ PBBS>
If you use this feature for monitoring PBBS traffic, the PBBS
prompt lines ("E.G. N4QQ PBBS>") will not be captured to disk. Do
not get your SYSOP to remove the ">" from the prompt line, or the
ZAP feature will then not work.
A happy face will be displayed in the "[S]" after the SAREX call
has been heard.
If you want to see an ORBITER menu, temporarily change the SAREX
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 69
call to be the same as your call and bring up the AMSAT-OSCAR
Menu.
17.2.4 Edit SAREX Capture-to-disk File
This option lets you edit the SAREX Capture-to-disk file as long
as it is less than 64 kBytes.
17.2.5 Zap SAREX ON/OFF
This option combines the "Set SAREX Attack Mode" and the "SAREX
Packets Capture to Disk ON/OFF" options in one fast operation.
17.2.6 Set Attack Mode to Connect/CQ
This option allows you to configure the SAREX Attack mode to
digipeat or CQ via the SAREX station as well as to try for
connect. Use the CQ feature to digipeat via MIR, and the connect
for the Space Shuttle. If the Attack Mode is set, LAN-LINK will
either try for a connect or send an unproto packet containing the
CQ text. If you want it to go through the SAREX Callsign you must
configure the UNPROTO parameter in the TNC. For example, to
attempt a digipeat via R2MIR, set 'UNPROTO CQ via R2MIR' from the
command mode.
17.3 SAREX Orbiter Features
This was the menu as seen by WA4SIR in orbit on STS-35. You need
the SAREX ROBOT EPROM for this menu to actually do anything to
the TNC. The EPROM may be available from The Radio Amateur
Satellite Corporation (AMSAT) for DX-pedition use. Other options
which control LAN-LINK parameters may be used without the SAREX
ROBOT EPROM.
In the Orbiter mode, LAN-LINK does not scan incoming text for the
"*** CONNECTED" and "*** DISCONNECTED" messages when the SAREX
Robot is active. This inhibits the bells and the capture-to-disk.
It also means that the Robot must be OFF for any :Q: code uploads
or downloads to occur.
17.3.1 Status Window Display
A flashing ">>" appears in the status window when the SAREX robot
is active. The SAREX Configuration boots up assuming that the
SAREX Robot is active (Default).
17.3.2 Alt-O Function key
The Alt-O Function Key brings up the Orbiter menu. This is a
faster route than the "Esc O" sequence.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 70
17.3.3 The Metabeacon
The Metabeacon is loaded from the contents of one of the META.00n
files. These files may be created by the LAN-LINK editor. When
loading, LAN-LINK will insert a pass character (^V) into the text
before a carriage return, so as not to end the packet before at
least 240 characters, and not more than 255 characters have been
output to the TNC. The maximum number of characters that can be
loaded into the Metabeacon is 1776. The maximum number of packets
in a Metabeacon is 7. You can also force a hard carriage return
or "end of packet" in the Metabeacon by inserting the "\"
(backslash) character, which will not be transmitted, into the
text.
17.3.4 SAREX Orbiter Menu
The following commands are active in the Orbiter Menu.
17.3.4.1 Activates Beacons/SAREX Robot: This option activates the
SAREX Robot and loads the Meta Beacon. This command is
designed for use when the SAREX is returned to the
regular frequency.
17.3.4.2 Set QRZ/QSL Beacon Interval: This command allows you to
change the beacon timer.
17.3.4.3 Set SAREX Call: This command allows you to change the
SAREX call. Don't use this command on orbit (it's for
ground use only).
17.3.4.4 Turn SAREX ROBOT OFF: The Robot must be turned ON and
OFF this way to synchronize LAN-LINK to the TNC. When
the Robot is turned OFF the following commands are sent
to the TNC by LAN-LINK.
USERS 1
|A
RO OFF
CMSG OFF
NO OFF
17.3.4.5 Set SAREX ROBOT Heard Count: This command lets you set
the Heard Count number.
17.3.4.6 Show I/O Status: Shows the callsign of the station
connected on each stream, the SAREX Robot state, the
number of USERS, the beacon timer value, the metabeacon
timer value and the CTEXT.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 71
17.3.4.7 ChecK Count: Shows both heard and worked counts.
17.3.4.8 List Heard Calls: Lists the callsigns of the last few
stations heard.
17.3.4.9 Load Metabeacon: This command loads the Metabeacon. You
will be prompted for a text file number in the META.00n
series. Enter a number 1-9 corresponding to META.001-
META.009. The 0 value is for file META.010. Note the
delays after loading the file to allow the TNC to
stabilize.
17.3.4.10 Show Worked Calls: Shows the last 35 or so callsigns
worked.
17.3.4.11 Turn SAREX ROBOT ON: The SAREX Robot must be turned ON
and OFF via the menu. When the Robot is turned ON the
following commands are sent to the TNC by LAN-LINK.
USERS 9
CONOK ON
CMSG ON
RO ON
NO ON
17.3.4.12 Stop Metabeacon: This command stops the metabeacon
transmission. When activated, the contents of the beacon
are dumped to the UNPROTO address (default SAREX) by the
TNC, rather like a regular PBBS dumping packets when a
user disconnects abnormally.
17.3.4.13 Set Metabeacon Interval: This command allows you to set
the metabeacon timer. It will be loaded into the TNC the
next time that the metabeacon is loaded. Even though
loaded into the TNC immediately, it does not take effect
till then.
17.3.4.14 Set SAREX ROBOT Worked Count: Lets you set the starting
number.
17.3.4.15 Set Connect TeXt: This is the text (CTEXT) that will be
transmitted to an incoming station when the ROBOT mode
is off. This option lets you set up a new text string to
go with the QSO number.
17.3.4.16 Selects Silent Mode: This command turns off the
beacons, the SAREX Robot and also stops the metabeacon.
This command is designed to be used just before any
prearranged packet activity.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 72
17.3.4.17 Restart TNC: This command RESTARTs the TNC, loads the
date from the computer's clock and turns the "EC OFF".
It seems to have no effect on the SAREX ROBOT and
counters, but does kill the metabeacon.
17.3.4.18 Capture QSL/QRZ Calls: This command initiates the log-
to-disk operation. It turns the capture-to-disk "on" and
sends the following commands to the TNC:- "DA", "SERW",
"SERH","MW", "MH". When the calls have stopped
scrolling, use Function key 1 to turn the capture-to-
disk off.
18.0 PARAMETER MENU
A typical Parameter Menu is shown in Figure 18. The colors used
for the option letter differentiate between those options that
are "remembered" in the SYS file and those that are only set
temporarily for the session. Type in the single letter to make
your choice.
Figure 18 A Typical Parameter Menu
A Send of LAN-LINK.OUT is ON 0 Change Band & Power
B Beacon/Robot Mode is OFF 1 Change PBBS/PacketCluster Parameters
C Clear Connect Count 2 Change Callsigns
D Digipeat Detect is OFF 3 Change Directories
E Command Echo is ON 4 Enter Common Calls
F BBS Zap Drop Link is ON 5 Change File Names
I Packet Beacon Control is ON 6 Change LAN-LINK Parameters
L Automatic Ctdsk is ON 7 Change PC Communications Parameters
M Set Message Count 8 Change Colors
N NODE Drop Link is OFF 9 Change SAREX Parameters
P Printer is OFF
Q QTC Snatch is ON U Update LAN-LINK.SYS
R :QSP: Relay Flag is ON V Verify Changes
S Sound is ON W Change Scan Words
T Contest Mode is OFF Z Time Id. is OFF
X DCD Flag is OFF ! Zap PBBS On Next Beacon is OFF
Y PBBS Snatch is ON + Misc. Flag is OFF
18.1 Turn Beacon Mode ON/OFF
This command toggles the beacon option for the automatic CQ
caller in the AMTOR, Pactor, G-TOR and Packet Communications
Modes. When it is active a "[B]" will be flashing in the status
window. In this mode, the Automatic CQ sequence will resume after
the AMTOR link is dropped or a Packet Communications Mode
disconnect.
In the Beacon Mode, the last few logbook entries will be
displayed in the logbook window which overlays the outgoing text
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 73
window at the bottom of the screen.
In the Packet Mode, the CTEXT message is the only transmission
from you that the other station will receive, so make it good and
don't forget to set "CMSG ON".
In the AMTOR Mailbox/Beacon Mode, the contents of the LAN-
LINK.TXT file will be transmitted to the station who called you.
The capture-to-disk will then be turned on to record one
transmission from that station. The QSO will then be logged to
the logbook file. Don't forget to check the entries in the
logbook and text in the LAN-LINK.RUN files in case the computer
made a mistake in recognizing the call sign of the other station.
The Beacon mode is designed to encourage people to QSY off the
crowded HF packet channels. Do not use it on a crowded HF channel
or on an active VHF channel. If you do, you will soon find that
other stations have set their TNCs to ignore your packets, and
you will not work anyone. You will just be a source of QRM and
will be known as such.
The Beacon mode is also designed for robot beacons on the higher
frequencies. For example, if you leave it running on 6 or 10
meters, you never know when a short opening will allow a QSO with
some part of the world, a DX contact you would otherwise have
missed. Don't leave it running on 20 Meters when the band is wide
open. Further applications are in meteor scatter and other
"exotic" communication modes.
If you are using the Beacon Mode in a special event station or
DX-pedition you may type characters into the transmit buffer,
while the other station is sending to you. When he, she, or even
it, turns it back to you, you will transmit those characters
before the sign-off sequence.
In all communications modes, the robot may be shut down by
stations connecting to you and telling you to QRT.
18.2 Clear Connect Counter
You use this option to reset the PACKET and AMTOR Beacon Mode
"connect has taken place indicator" and QTC Snatch counters.
These are the flashing "[C]" and "[Q]" displays in the status
window. Whenever someone else connects or links up to you the
"[C]" display will be incremented. The number shown with the "C"
is the number of connects that have taken place since the
Indicator was last reset. If a "happy face" is flashing along
with the connect count, your "target station" was amongst those
connecting. The "[Q]" indicator alerts you to the fact that LAN-
LINK tried to connect to another station after recognizing your
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 74
call in a mail beacon. Both are reset by this option. If you are
monitoring Packet traffic on a channel, you may not notice that a
connect has previously taken place. These indicators alert you to
check the contents of the Incoming mail file ("yourcall.OUT") for
any incoming messages.
If the "Q" count is much greater than the "C" count, you may be
copying a beacon from a station that you cannot connect with
directly.
18.3 TNC Custom Line (TNC Parameter)
This line has different effects depending on which TNC you are
using. To set the line, add the numbers up for the parameters you
want, and put the total in line 32.
18.3.1 All TNC's
TNC Sync shift (128)
LAN-LINK normally ensures that the Transmitter and Receiver
data sense are in phase. This presupposes AFSK operation. If
you are running FSK and need them out of phase, set this
byte to 128. If this line includes the number 128, LAN-LINK
will NOT set the receiver shift when you change modes.
Zap Stay Up (64)
If you include the number 64 in this line, LAN-LINK will
default to staying connected to a PBBS when the Zap sequence
ends. Use this parameter setting if the messages contain a
lot of ">" characters at the end of lines and LAN-LINK is
faked into thinking the messages ended prematurely.
TNC initialize Date (32)
LAN-LINK normally sets the time of day clock in the TNC from
the PC during initialization. If you don't want LAN-LINK to
set the TNC time of day clock, include the value 32 in this
line.
18.3.2 PK-232, PK-900 and DSP 2232
PK-232 Digipeat Display Flag (1)
Set this line to 1 to activate this feature, 0 to inhibit
it. If the Digipeat Display is active, any signals digi-
peated through you will be stored to the LAN-LINK.RUN file
and a "beep" will be sounded for each packet being
digipeated. The status window will also contain a "[D]".
PK-232 Converse Mode Default (2)
LAN-LINK runs the PK 232 is command mode in the RTTY an CW
modes. Function key 7 (F7) allows you to set the PK 232 into
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 75
the converse mode. The MFJ 1278 and KAM operate in the
Converse mode in all communications modes. If you set this
bit to 2, LAN-LINK will run the PK-232 in the converse mode
in all modes, and you will not need to use F7 to enter the
converse mode before transmitting.
PK-232 Serial Port Initialization (4)
If this bit is set to 4, LAN-LINK will assume there are no
batteries in the PK-232 and issue the '* * *' sequence to
the PK-232 on start up. If this bit is not set, LAN-LINK
will assume the PK-232 contains batteries and will not try
to synchronize the PC to PK-232 serial port.
This feature was removed from LAN-LINK in 2.00 in response
to numerous users who had batteries in their PK-232's and
didn't want to see the initialization sequence. Then came
the complaints from the users who didn't have batteries in
their PK-232's.
PK-232 XMITOK Flag (8)
In the CW communications mode, you may have to change the
value of the PK-232 XMITOK Parameter depending on how you
connect the PK-232 to your transmitter. This LAN-LINK
parameter determines if LAN-LINK instructs the PK-232 to
turn the XMITOK PK-232 parameter on and off when entering
and leaving the CW communications Mode. You may temporarily
change the value of the XMITOK Flag in the CW menu to set
things up.
As an example, to configure LAN-LINK to initialize the PK-
232 serial port (4) and default to the Converse Mode (2),
Set this parameter to 4+2 or 6.
18.4.2 KAM
KAM Set LFADD (2)
If this bit is set, LAN-LINK will send a 'LFADD ON' command
to the KAM when you enter the BAUDOT communications mode,
and send a 'LFADD OFF' command when you exit that mode to
another one.
KAM Pre 3.0 EPROM (4)
If your KAM contains an EPROM with a Revision number of less
than 3.0, then set this bit. LAN-LINK will issue NODE
commands when selecting SOLO mode. You must set this bit if
you plan to use the mailbox in the KAM, or the traffic on
frequency will fill the memory in the KAM, and people will
not be able to leave you any messages.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 76
18.4.3 MFJ 1278
MFJ Radio Port (1)
This bit allows MFJ users to set the default radio port for
VHF. Set this bit to 1 to assign Radio 1 to VHF (Radio 2 to
HF). Set this bit to 0 to assign Radio 2 to VHF (Radio 1 to
HF).
MFJ Echo ON/OFF Flag (2)
Some versions of the MFJ firmware require 'ECHO ON' in
AMTOR. IF bit 2 is set, LAN-LINK will command 'ECHO ON'
before entering AMTOR, and will command 'ECHO OFF' when
leaving AMTOR, if you switch modes via the Menu.
MFJ AMTOR Converse Flag (4)
This bit configures the MFJ to send the CONVERSE Command
when someone connects in the AMTOR Mode.
18.4 Turn Beacon Control ON/OFF
This option toggles the LAN-LINK Handshake features. When they
are on (default), the Connect handshake message
[ZCZ] *** LAN-LINK 2.32>
will be transmitted on incoming connects. The beacon text and
time will be controlled by LAN-LINK as a function of the messages
you have posted on your system. When they are off, LAN-LINK does
not do anything to your beacon, nor does it transmit the
handshake.
18.5 Turn Command Echo ON/OFF
This option toggles the LAN-LINK "Command ECHO flag" ON and OFF
(not the ECHO parameter in the TNC). If the Command Echo flag is
set, the commands and (contents of) files LAN-LINK sends to the
TNC will be displayed in the outgoing window. Set this flag to
see how LAN-LINK commands the TNC in the different modes.
18.6 Change Keyboard Beep Count
LAN-LINK counts the number of characters entered on a line at the
keyboard. When it gets to a preset value it will beep, signaling
you to start a new line. If you have the Word wrap option set, it
will also automatically insert a "carriage return/line feed"
character sequence into the outgoing text for you. This option
changes the value that the keyboard beep counter is compared with
to sound the audio signal.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 77
18.7 Set Message Count
As an alternative to Function Key 8 (F8) or Alt-D, using this
option will also load a QTC "Mail" list into your Packet Communi-
cations Mode Beacon and initiate a beacon transmission every 30
minutes (Refer to the BTEXT command in the TNC manual). If no
messages are present, or the only message is to you (incoming or
snatched), beacon transmissions are inhibited. This conforms to
good operating practice on crowded Packet channels.
18.8 Turn Node Drop Link ON/OFF
When connecting via a Node, the normal way of operating is to
disconnect if the connect attempt fails. You may configure the
Node connect attempt flag to stay connected at the node where the
failure occurred. Use the normal mode when trying to get through
on a known path, and the stay alive mode when exploring Node
circuits.
18.9 Turn Printer ON/OFF
This option toggles the printer ON and OFF. When the printer is
turned on, any incoming data will be printed in real time. If you
intend to print files received at 1200 baud in the Packet
Communications Mode, use a print spooler or you may lose data.
The printer is automatically turned off in the Packet Mode when a
disconnect occurs.
18.10 Turn QTC Snatch ON/OFF
This option toggles the QTC Snatch flag ON and OFF. If the QTC
Snatch flag is enabled, LAN-LINK scans the contents of packets
appearing in the Inwindow on the screen while the terminal is
disconnected. Should it recognize the three text strings "LAN-
LINK", ":QTC:", and "YOURCALLSIGN" in the contents of a packet,
it will then issue a connect request to the callsign of the LAN-
LINK station that originated the beacon transmission. If the
connect is made, the other station will send you the message
automatically which LAN-LINK will "capture to disk". The connect
will time out and terminate a few minutes later.
The normal connect request will be made DIRECT to the station. If
you expect messages from stations you can only connect with via a
digipeater, place the path in your LAN-LINK.DIR directory file.
It should be there anyhow if you connect to the station
regularly. For example, if you expect messages from 4Z4ZB whom
you can only work if digipeated via 4X1AA then place an entry
like "4Z4ZB 4Z4ZB V 4X1AA" in the LAN-LINK.DIR file.
The QTC Snatch leaves your messages in a message file
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 78
YOURCALL.OUT. It is triggered by the first ">" in the initial
connect response of "LAN-LINK 2.00R>" and terminated by the
"over" at the end of the message e.g. G3ZCZ/W8>. If you train
stations not using LAN-LINK who want to leave you messages to
trigger your QTC-Snatch, by transmitting the following un-
addressed packet
LAN-LINK :QTC: YOURCALL
your system will connect to them. (For example to leave a message
for me, they would send
LAN-LINK :QTC: G3ZCZ
as an un-addressed packet [in Converse Mode when not connected,
or in their beacon text].)
If they then send you a ">" on a line by itself, followed by the
message itself, and terminated by another ">" as the last
character of the line, the message will end up in a message file
rather than in the LAN-LINK.RUN file and you can scan it fast
using Alt-M (Message Scan Menu Options). It goes without saying
that the message itself should not contain the ">" character at
the end of a line. If it does, by the way, the first part of the
message will be in the message file, while the remainder will be
in the LAN- LINK.RUN file.
18.11 Turn :QSP: Relay Flag ON/OFF
This option toggles the Store and forward Message Relay
Capability of your system ON and OFF. If the Message Relay
Capability is active (toggled on), any one who connects can store
a message in your system using the ":QSP: CALLSIGN" NC/L command.
If the Message Relay Capability is not active anyone who attempts
to ":QSP:" a message will receive a ":QNO: error" message. The
status display window will show a "[R]" when the Message Relay
Capability is active. The default state for the Message Relay
Capability is loaded from the LAN-LINK.SYS file.
When the Store and forward capability is active, the suffix "R"
will be added to the "[ZCZ] *** LAN-LINK 2.32". i.e., "[ZCZ] ***
LAN-LINK 2.32R" message received by anyone connecting to your
system to notify them that they can store messages. In this
manner they don't have to try to leave a message and then get
":QNO:" error message to find out that the feature is toggled
off.
Remember, if you configure your computer to store and forward
messages, you have a moral obligation to deliver them.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 79
18.12 Turn Sound ON/OFF
This option toggles the sound ON and OFF. If the sound is off, a
flashing indicator will be displayed in the Status Window. When
the sound is toggled on again, a chime will sound to verify the
audio.
18.13 Turn Contest Mode ON/OFF
This option first toggles the Contest Mode. If the Contest Mode
is active, the word "TEST" and the number of the next QSO will be
displayed in the status window. When the Contest Mode is toggled
on, this command prompts you to set the starting QSO number, and
the standard message that will be transmitted as part of the
exchange of messages during the contest. The QSO number will be
incremented each time you log a contact.
The contest feature is toggled off the next time you select this
feature.
While these features do give you some semiautomatic contest
operation by using command keys, there is no checking of
callsigns for duplicates built into the program. You may do that
by using the Alt-S hot key.
In a contest, you enter the callsigns and call the other station
in the normal manner, then use the "End" Key to transmit the
exchange (QSO number and standard text). LAN-LINK will only
transmit the contest text in this manner. If you want to add a
"K" or "KN", you will need to put it in the contest text string.
It is also advisable to use a different log file for each contest
to cut down the search time. The contest QSO number increments
each time you log the QSO (Alt-L).
You may put the Contest Mode into automatic if you are operating
AMTOR or packet. To do so, use the Alt-O function key.
The following special character sequences can be entered in the
contest text string.
18.13.1 ##
A "##" will be replaced by the QSO number when the text is
transmitted.
18.13.2 #1
A "#1" will be replaced by the callsign of the station being
worked in the contest text string.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 80
18.13.3 #T
A "#T" will be replaced by the date and time as read from the PC
time-of-day clock and converted to Universal Coordinated Time
(UTC). A sample time text is "03-Mar-92 03:13".
For example, use the following entries for the following
contests;
"##1 UR ##A" ... in the Sweepstakes,
"5905" ... in the WAZ,
"59 MD" ... in the ARRL DX, and
"59 ##" ... in the WPX.
As an example, if I (W3/G3ZCZ) am in the Sweepstakes contest, and
my Contest text line is,
"##1 UR ##A W3/G3ZCZ 68 MDC".
If the next QSO number is 345, and I am working KW3C, when I
touch the "End" key, LAN-LINK would transmit the following line
"KW3C UR 345A W3/G3ZCZ 68 MDC".
18.14 Turn DCD Flag ON/OFF
If you are using a PK-232 then this flag should be set to ON. If
you are using a KAM, this flag should be set to OFF. If you are
using another TNC, and if you can set the TNC so that pin 8 on
the RS-232 interface changes state when connected, do so, and set
this flag to ON. If you can't, then set this flag to OFF. If this
flag is OFF, the multiple-connect modes will not work so don't
attempt to invoke them. If this flag is OFF, the words "***
CONNECTED" and "*** DISCONNECTED" when seen in the LAN may cause
spurious apparent connects and disconnects in LAN-LINK.
18.15 Turn PBBS Snatch ON/OFF
When the PBBS Mail Snatch is enabled, and a PBBS sends a packet
announcing "Mail", if your callsign is in the first line of that
message, LAN-LINK will issue a connect request (again via the
path in LAN-LINK.DIR) to that PBBS. When connected, it will act
as if you have initiated a Zap PBBS command. The Zap counter will
be incremented each time a PBBS Mail Snatch takes place.
If the PBBS Mail beacon has an extra line in it (between the
header and the list of calls) as follows, the PBBS Mail snatch
will not work.
On the other hand, if N4FG is monitoring the LAN, and a message
is posted for any callsign containing the character string "N4FG"
such as N4FGA, N4FG will respond to the message. This gives rise
to a lock out situation, because N4FG will respond to the beacon,
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 81
go through the sequence described in the Zap PBBS section and
disconnect. The beacon message will not be cleared because it was
not read, so the next mail beacon from the PBBS will contain the
call N4FGA, and N4FG will once again respond to it.
Should you be unlucky and happen to be in this situation, disable
the PBBS Snatch flag and set a Periodic Event to Zap your PBBS
sometime in the middle of the night. Alternatively, when you come
into the shack and the PBBS is in use, set the "Zap PBBS on Next
Mail Beacon" parameter to ON.
18.16 Turn Time Id. ON/OFF
This option allows you to determine if the callsign sequence
transmitted using Function key 3 (F3) will contain a date/time
stamp. If the Id. is set ON a date/time stamp will be
transmitted.
18.17 Turn Automatic Capture-to-Disk Flag ON/OFF
This option allows you to turn the automatic "capture-to-disk"
feature ON and OFF.
18.18 Change PBBS Parameters
This sub-menu allows you to change the PBBS Parameters, as
described in the following paragraphs.
18.18.1 Local PBBS Callsign
This option lets you change the call of the local PBBS. This is
the call that LAN-LINK will show in the prompt for the "Zap"
command.
18.18.2 Mail-Snatch Trigger Word
You can set the Mail-Snatch Trigger in the PBBS Mail beacon. Most
PBBSs use word "Mail" and a string of calls to indicate the
presence of messages. If your PBBS uses something else, you may
customize LAN-LINK on this line to tell it what word your PBBS
uses. This word is case sensitive. If your PBBS uses "QTC"
instead of "Mail", you may end up calling yourself if you
disconnect while traffic is flowing on the LAN.
18.18.3 Read Request Command
This is the command LAN-LINK issues to the PBBS during a Zap
sequence to request your mail. The default value is "RM" for Read
Mine. On a WA7MBL type PBBS you may change it to "VM" for a
Verbose Read of the full packet headers. On a W0RLI PBBS you may
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 82
change it to RN to only request new messages. If you do change
it, use the "V" option in the Parameters Menu to make sure it is
correct. If it isn't correct, the Zap PBBS feature will not work.
18.18.4 Read Bulletin Request Command
This is the command LAN-LINK issues to the PBBS during a Zap
sequence to read bulletins identified by the scan words. The
default value is "R" for Read. For a Verbose Read of the full
packet headers on a WA7MBL type PBBS, change it to "V"; on a
W0RLI type PBBS change it to "RH".
18.18.5 PBBS Subject String
When you enter a message into a PBBS, you first use the "S"
command. The PBBS then sends you a reply asking you for some
information about the PBBS; typically the subject of the message.
When you have entered the subject, the PBBS then asks you for the
rest of the message. This line is used in the Zap sequence and is
a unique word seen in the text that the PBBS sends you asking for
the subject.
18.18.6 PBBS Message String
When you enter a message into a PBBS, you first use the "S"
command. The PBBS then sends you a reply asking you for some
information about the PBBS; typically the subject of the message.
When you have entered the subject, the PBBS then asks you for the
rest of the message. This line is used in the Zap sequence and is
a unique word seen in the text that the PBBS sends you asking for
the text of the message.
18.19 Change Callsigns
This sub-menu allows you to change the Callsign and AMTOR SELCAL,
as described in the following paragraphs.
18.19.1 Callsign
The default callsign is G8BTB. Please do not use G8BTB. Replace
G8BTB with yours. This is the callsign that will be used in the
non packet modes. You may use "portable designators" such as
G3ZCZ/A, G3ZCZ/W3, W3/G3ZCZ or G3ZCZ/4X, which you cannot do in
Packet.
This is the call that will be monitored for in the Digipeat
Monitoring Mode. In this Mode, which is toggled on and off by the
selection of the "D" Option included in the Parameter Menu (PK-
232 only), if someone uses you as a digipeater while you are not
connected to anyone else, the event will be logged to disk. This
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 83
Mode will only work if your callsign as stored in this line is a
valid (uppercase only) packet callsign.
For example, in the PK-232, if the callsign is G3ZCZ then the
sequence >G3ZCZ> will be recognized as a digipeat and the event
logged. Thus 4X6AA*>G3ZCZ>4Z4ZB would be logged as a digipeat
event.
Store your callsign using UPPERCASE characters if you want the
"DIGIPEAT DETECT" option to work (i.e. G3ZCZ). If you use lower
case (i.e. g3zcz), recognition will never take place. The TNC
displays all callsigns in upper case in the non packet communica-
tions modes.
If you are using an SSID (e.g. G3ZCZ-8) in the Packet
Communications Mode, you should enter the whole call INCLUDING
the SSID.
18.19.2 The SELCAL
This is your AMTOR SELCAL. LAN-LINK will try to guess it and
prompt you with a SELCAL configured for your callsign. If you
want a different one, overwrite the prompted version.
If you are not using a PK-232 or KAM or the MFJ1278, you don't
have to change anything, but the SELCAL line must still be in the
Configuration file.
18.19.3 The PacketCluster Call
This option allows you to change the default PacketCluster Call
without connecting to it.
18.20 Change Directories
This sub-menu allows you to change the Directories used by LAN-
LINK, as described in the following paragraph.
18.20.1 Capture-to-disk files Directory
This is the drive and directory that LAN-LINK will put the *.RUN
capture-to-disk files. Note: the last "\" MUST be present if you
are using a different sub-directory.
18.20.2 QBM Download Directory
This is the directory the :QBM: command will search to find a
file to be downloaded. The default directory for the files is
\LAN-LINK\FILES\. Note: the last "\" MUST be present.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 84
18.21 Enter Common Calls
Each time you call another station, LAN-LINK remembers it (up to
the last 16). When you update the SYS file, those calls will be
saved to disk. You can use this option to add calls, delete calls
or edit calls in the list. Use the "Delete" key to delete a call.
18.22 Change File Names
This sub-menu allows you to change the default file names used by
LAN-LINK, as described in the following paragraphs.
18.22.1 VHF Logbook File (VHF.DBF)
This is the name of the file to be used as your VHF Packet
logbook.
18.22.2 HF Logbook File (HF.DBF)
This is the name of the file to be used as your HF logbook. It is
used for all HF modes, including HF packet.
18.22.3 Path Directory File (LAN-LINK.DIR)
This is the name of the file used as your call directory.
18.22.4 Brag Tape (LAN-LINK.TXT)
This is the name of the file used as your brag tape.
18.22.5 QBU Upload File Name (QBU-TX.BAT)
This is the name of the batch file used to initiate a QBU.
18.22.6 QBU Download File Name (QBU-RX.BAT)
This is the name of the batch file used when a :QBU: command is
received from a remote station.
18.23 Change LAN-LINK Parameters
This sub-menu allows you to change the LAN-LINK Parameters, as
described in the following paragraphs.
18.23.1 Change CQ Text
This feature allows you to change the contents of the CQ text
message string. This is the message string that is transmitted
along with the CQ call. Think of this message as a CQTEXT line.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 85
18.23.2 Set CQ Delay Time (Seconds)
This option allows you to change the time (seconds) that the LAN-
LINK waits for a response after a CQ call until the following one
is transmitted. The default value (in minutes and seconds) is
loaded from the LAN-LINK.SYS file.
18.23.3 Set CQ Delay Time (Minutes)
This option allows you to change the time (minutes) that the LAN-
LINK waits for a response after a CQ call until the following one
is transmitted. The default value (in minutes and seconds) is
loaded from the LAN-LINK.SYS file.
18.23.4 Set Connect Time Timeout (Minutes)
This option allows you to change the time (minutes) that the LAN-
LINK waits for a response in a packet connect before issuing a
Disconnect command. The default value is loaded from the LAN-
LINK.SYS file.
18.23.5 Set Number of Lines in a Non-Contest CQ Call
This option allows you to change the number of lines in a non-
contest CQ call from the default value of 3 to any number you
wish. The default value is loaded from the LAN-LINK.SYS file.
18.23.6 Keyboard Beep Character Count
When your typing at the keyboard gets to a point where you may
overrun the normal line length, LAN-LINK issues a beep to remind
you to touch the "Enter" key. This option allows you to change
the number of characters you can type in a line before the beep
sounds. Note the beep will not sound if the sound flag is
inhibited.
18.23.7 Word Wrap Mode
This option allows you to change the word wrap mode. It is really
more of a "force carriage return" parameter, rather than "word
wrap". There are four options as follows:
18.23.7.1 Off: Word wrap is off.
18.23.7.2 AutoCR: LAN-LINK will insert an "Enter" character for
you into the outgoing text when you enter the first
space character after the beep has sounded.
18.23.7.3 Word: LAN-LINK will hold all entered text until you
either type a space character or touch the "Enter" key.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 86
At that time LAN-LINK will send the word to the TNC.
18.23.7.4 Line: LAN-LINK will hold all entered text until you
either touch the "Enter" key or the beep sounds. At that
time LAN-LINK will send the word to the TNC.
Set this parameter value as follows,
0 = OFF,
1 = AutoCR,
2 = Word,
3 = Line.
18.23.8 Set Shut Down Mode (QRT Flag)
This option allows you to customize the shut down and start up
sequences of the TNC as described in the following sections. If
the Shut down mode is not set to 1, you also have the option to
customize the packet terminal mode.
18.23.8.1 State 0: On shut down, turns the TNC into a VHF Digi-
peater and turns CONOK OFF (CFROM NONE for the PK-232).
In this condition the TNC will reject connect requests.
On start up turns CONOK or CFROM on.
18.23.8.2 State 1: Does not send any commands to the TNC on shut
down or start up.
18.23.8.3 State 2: On shut down, sends CMSG ON to the TNC. On
start up, sends CMSG OFF to the TNC.
18.23.8.4 State 3: On shut down, turns on the mailbox in the TNC.
On start up turns off the mailbox.
18.23.8.5 State 4: On shut down, turns on the mailbox in the TNC
and puts the TNC into the SOLO Mode so that the internal
buffer in the TNC does not fill with on-the-air traffic.
On start up turns off the mailbox.
18.23.9 Set Default Users
This option allows you to set the maximum number of multiple
users that can be connected to your TNC at the same time, and to
configure the default start up mode of the program. If this
parameter is set to 1, LAN-LINK will configure itself to the
single user mode, and set the maximum number of users to 9. If
this parameter is set to any number other that 1, LAN-LINK will
assume that value to be the maximum number of allowed connects,
and configure itself in the Multiple user Mode (equivalent to the
TNC Menu Option 0).
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 87
18.23.10 Set UTC Offset
This parameter contains the difference in hours between Universal
Co-ordinated Time (UTC) and your local time. For example, if you
are located on the east coast of the U.S.A., and it is winter,
you are in the Eastern Standard Time (EST) Zone, which is 5 hours
behind UTC. In this case, the value of the UTC Offset parameter
is 5. Don't forget to change this parameter when the clocks are
adjusted each spring and autumn.
18.23.11 VHF Packet Length
This option allows you to change the default VHF packet length.
The TNC has a maximum permissible value of 255. Set the parameter
to 127 or 255.
18.23.12 HF Packet Length
This option allows you to change the default HF packet length.
The default value of about 30 seems to be optimal.
18.23.13 Beacon Time
This option allows you to change the default beacon time. The KAM
requires a value in minutes, all other TNCs in tens of seconds.
Use good operating practice and don't beacon too often. Every 30
minutes on a well used channel is more than enough.
18.23.14 Custom Prompt before "Over"
This option allows you to add a word or two (up to 20 characters)
before the ">" in packet or the "+?" in AMTOR. If you are working
an AMTOR APLINK PBBS, clear this feature by changing it to a
space character.
18.23.15 Packet Cluster DX Alert Mode
This parameter determines the action LAN-LINK takes when you are
connected to a PacketCluster, and a DX Alert message shows up.
The states are 0, 1, 2, or 3.
If it is 0, LAN-LINK takes no action at all. In all other states,
LAN-LINK splits the prefix from the DX callsign, searches the HF
logbook for the prefix and posts a message in the status window
(in the Alert Call color) as follows: Prefix, Logbook Status, DX
callsign. The logbook status shows up as 'Q' for QSLd, 'W' for
worked and '?' for not in log. You can configure LAN-LINK to
generate an audible alarm for each condition to save you
monitoring the screen. If the Sound is inhibited, the audible
alarm will also be inhibited. The visual display and audio alarms
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 88
are controlled by this parameter as shown below.
State QSLd (Q) Worked (W) Not in Log (?)
0 No Action No Action No Action
1 Audio + Display Audio +Display Audio + Display
2 Display Audio + Display Audio + Display
3 Display Display Audio + Display
You can customize the CW tone and speed, by changing the states
of the "Packet Cluster DX Alert Tone CW Dit time" and "Packet
Cluster DX Alert Tone CW Note" parameters in the LAN-LINK.SYS
File.
In this version of LAN-LINK, the prefix scan is simple minded, so
set this parameter to 3 to get used to it, then set it to 1.
18.24 Change PC Communications Parameters
This sub-menu allows you to change the Communications Parameters
between the PC and the TNC, as described in the following
paragraphs.
18.24.1 The Communications Port
This is the default Communications port. The default value is 1.
You may set it at any value between 1 and 4. If you only have one
serial port in your PC, set the parameter to "1" even if your
card is configured as Com2. LAN-LINK will ALWAYS assume Com1 for
a single card. If you use a different port instead of Com1, and
plan to do binary transfers, don't forget to customize the
QZ*.BAT files.
The default Com3 and Com4 default PC port values are as follows.
Port Address(Hex) Address (Decimal) IRQ
Com3 3E8 1000 4
Com4 2E8 744 3
If you set the port number to 0, LAN-LINK will not accept or
transmit any character to the serial port. All other features
will work.
18.24.2 The Terminal Baud Rate
This Parameter tells LAN-LINK what baud rate the TNC is set to.
This is the baud rate on the RS-232 line between the TNC and the
PC. Valid baud rates for LAN-LINK are 300, 1200, 2400, 4800, 9600
and 19,200. If you specify something else LAN-LINK will default
to 1200.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 89
You may experience problems when using baud rates greater than
1200. It depends on the CPU clock rate, any TSR's in the PC, and
the I/O card in the PC. LAN-LINK scans the incoming text
constantly, something which requires time. My PK-232, when used
with my XT Clone at 10MHz, does not like baud rates faster than
2400, and sometimes not even that. The PK-232 seems to drop the
first character of some lines at 4800 baud. Use 1200 until you
have tested, and are sure that a faster one will work.
This program has been tested on a TNC2 and an MFJ1278 using a
terminal baud rate of 9600 baud and worked correctly. It also
works correctly with a KAM at 2400 Baud.
If you use a different rate instead of 1200, and plan to do
binary transfers, don't forget to customize the QZ*.BAT files.
18.24.3 TNC Data Bits
You can set the number of data bits on the RS-232 line between
the PC and TNC to 7 or 8. Use 7 with a TNC2 if you have problems
with Greek characters. Set this value to either 7 or 8.
18.24.4 TNC Parity
Use this parameter to set the Parity bit on the RS-232 line
between the PC and TNC. Enter the letter corresponding to the
desired parity. N = None, O = Odd, E = Even, M = Mark, S = Space.
18.24.5 Number of TNC Stop Bits
You can set the number of stop bits on the RS-232 line between
the PC and the TNC to 1 or 2. Use 1 at all terminal (not packet)
baud rates except 300. Set this value to 1 or 2.
18.25 Change Colors
This option lets you change the default colors. A display of all
of the combinations is shown on the left side of the screen. You
will then be prompted to sequence through each window/message
color that can be customized. Enter the number shown in the
combination window followed by the "Enter" key to set a value. If
you don't wish to make a change, just press the "Enter" Key.
The following identifications are made to the color choices:
18.25.1 OutWindow Color
This is the color of the text (typed at the keyboard) in the
outgoing window.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 90
18.25.2 StatusWindow Color
This is the color of the Status Window.
18.25.3 PromptWindow Color
This is the color of most of the menus.
18.25.4 LogWindow Color
This is the color of the text in the log window.
18.25.5 InWindow Color
This is the color of the text in the window showing the incoming
characters.
18.25.6 ScrollBack Window Color
This is the color of the text in the Scroll back window.
18.25.7 MHWindow Color
This is the color of the text in the monitor heard calls (MH)
window.
18.25.8 Alarmwindow Color
This is the color of the text in the Error and Alarm window.
18.25.9 BottomWindow Color
This is the color of the text in the prompt line at the bottom of
the screen.
18.25.10 Emphasis Color
This is the color of the emphasized text in the Menu windows.
18.25.11 Prompt Color
This is the color of the prompt text in the Menu windows.
18.25.12 Option Color
This is the color of selected option text in the Menu windows.
18.25.13 Connected Text Color
This is the color of the text in the incoming window when
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 91
connected in the packet communications modes.
18.25.14 Computer Color
This is the color of the computer generated text in the outgoing
window when the Command Echo Flag option is enabled.
18.25.15 VHF Header Color
This is the color of the VHF Header lines in the Incoming window
when not connected.
18.25.16 HF Header Color
This is the color of the HF Header lines in the Incoming window
when not connected.
18.25.17 Alert Call Color
This is the color of the packet header lines containing the Alert
call in the Incoming window when not connected. It is also the
color of the non-permanent Parameter Menu prompts.
18.25.18 Outgoing Text Color
This is the color of the outgoing text echoed in the Incoming
window in the AMTOR Communications Mode.
18.25.19 Multi I/O Stream Color[1]
This is the color of the text lines in the Incoming window in the
Multiconnect Mode when connected to I/O stream 1.
18.25.20 Multi I/O Stream Color[2]
This is the color of the text lines in the Incoming window in the
Multiconnect Mode when connected to I/O stream 2.
18.25.21 Multi I/O Stream Color[3]
This is the color of the text lines in the Incoming window in the
Multiconnect Mode when connected to I/O stream 3.
18.25.22 Multi I/O Stream Color[4]
This is the color of the text lines in the Incoming window in the
Multiconnect Mode when connected to I/O stream 4.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 92
18.25.23 Multi I/O Stream Color[5]
This is the color of the text lines in the Incoming window in the
Multiconnect Mode when connected to I/O stream 5.
18.25.24 Multi I/O Stream Color[6]
This is the color of the text lines in the Incoming window in the
Multiconnect Mode when connected to I/O stream 6.
18.25.25 Multi I/O Stream Color[7]
This is the color of the text lines in the Incoming window in the
Multiconnect Mode when connected to I/O stream 7.
18.25.26 Multi I/O Stream Color[8]
This is the color of the text lines in the Incoming window in the
Multiconnect Mode when connected to I/O stream 8.
18.25.27 Multi I/O Stream Color[9]
This is the color of the text lines in the Incoming window in the
Multiconnect Mode when connected to I/O stream 9.
18.25.28 Multi I/O Stream Color[10]
This is the color of the text lines in the Incoming window in the
Multiconnect Mode when connected to I/O stream 10.
When you change the colors, LAN-LINK does not overwrite all
existing windows. If you want to be sure of seeing the changed
colors, save the color changes using the Update option, and then
exit from and reload LAN-LINK.
18.26 Change SAREX Parameters
This sub-menu allows you to change the SAREX Ground Station
parameters, as described in the following paragraphs.
18.26.1 SAREX CallSign
This is the callsign of the SAREX station.
18.26.2 Change SAREX Capture to Disk File
This option lets you change the name of the SAREX Capture- to-
disk file. Don't change file names while "capture-to-disk" is in
progress (when a flashing "[S]" in present in the status window),
or the old one will stay open and may not close properly when
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 93
LAN-LINK is terminated, resulting in data loss.
18.27 Update Configuration File
Use this option to save the changes (permanently) in the
configuration file (LAN-LINK.SYS). Activate it twice to see most
of the changes.
18.28 Verify Changes
This feature lets you display how LAN-LINK was configured by the
LAN-LINK.SYS file. It also displays the state of any flags you
have set/reset if they are not already shown in the Status window
or Parameter Menu.
18.29 Change Scan Words
In the ZAP PBBS feature you can ask the program to scan the lines
read from the PBBS and if it sees any of the scan words in the
line, it will queue a request for that bulletin by number. You
can only set 16 such Scan words (should be enough) and request up
to 255 messages/bulletins at a time.
Color in the scan words. The colors shown in the Scan Word window
match the colors the lines containing those scan words are
written in during a BBS Zap. The colors are the multi stream
colors.
Use the "Delete" key to delete a word from the list.
Words that show up in the PBBS prompt line cannot be used as scan
words. For example, if your PBBS prompts you with
N4QQ PBBS>
then "N4QQ" and "BBS" should not be used as Scan Words.
Don't leave a blank line in the Scan Word section of the
configuration file.
18.30 Turn Miscellaneous Flag ON/OFF
The Miscellaneous Flag performs several different functions in
the different Communications modes as follows.
18.30.1 All Modes:- Debug or state-sequence numbers
Shows two debug or state-sequence numbers in left hand corner of
the status window in the format N-M]. N is the BBS State and M is
the Communications State. These are used to figure out what went
wrong in the automatic sequences. If an automatic sequence fails
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 94
to work, set the miscellaneous flag, and observe the state in
which LAN-LINK seems to hang. It will be waiting for something,
and you should get a clue as to what, from Table 18.30.1. BBS
State (N) numbers are shown in Table 18.30.1-A and the
Communications states are shown in Table 18.30.1-B.
Table 18.30.1-A BBS States
1 Connected to BBS waiting for first '>'
2 Receiving incoming messages
3 Receiving list of new messages
4 Receiving your messages (in case missed some)
5 Custom command (i.e. KM)
6 LAN-LINK QTC Snatch in progress
7 Receiving Mail going to YOURCALL.OUT
8 :QDB: waiting for QRV/QNO
9 :QDB: sending file waiting for QSL/QNO
10 AUto UPload Opening BBS.BBS command file
11 AUto UPload sending one line command
12 AUto UPload sending subject line of message
13 AUto UPload sending message
14 AUto UPload waiting for last '>' before disconnecting
22 Receiving file
25 Packet cluster connect waiting for first '>'
26 Packet cluster connect waiting for first '>'
Table 18.30.1-B Communications States
0 Disconnected packet mode or normal non packet mode.
1 Connected in packet mode
2 Trying to connect in packet mode
3 Trying to disconnect in packet mode
4 Sending mail file in packet mode
5 ARQ called someone, or in QSO
6 Connected in autocq mode
7 Calling autocq in packet
8 Sending file in autocq
9 Waiting for reply in autocq packet
10 Autocq non packet sending CQ message
11 Autocq non packet waiting for reply
12 SELCAL waiting for ZCZC or YOURCALL
13 SELCAL waiting for NNNN
14 Autocq AMTOR sending bragtape
15 Autocq AMTOR receiving message
16 Autocq AMTOR requesting repeat of his_call
17 Autocq MFJ1278/KAM waiting for 73 to complete and sign off
21 QRU mode packet
22 Calling someone in pactor
25 AMTOR sending :QQQ: response
26 QRU mode packet
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 95
18.30.2 BAUDOT Mode:- Navy MARS Protocol Verify
When the flag is set, and the BAUDOT Navy MARS option is enabled,
the character string ":CR:" will be displayed in the outgoing
window each time a carriage return character is received in the
incoming window. Similarly, every time a line feed character is
received, a ":LF:" will be displayed in the incoming window.
You may use this feature to verify that another station is
sending files using the correct protocol. If you do, make sure
that you tell the PK-232 not to add a line feed to incoming
carriage returns by setting the ALFD parameter to OFF in the Com-
mand Mode. You will have to set "ALFD ON" again when you change
to other communications modes, or all incoming lines will
overwrite each other.
18.31 Change Band/Mode
This option is used to set the band and radio mode without
invoking the Log Menu. You can use it when changing bands on HF
before logging a new QSO. The value is not remembered when you
shut LAN-LINK down, unless you log the QSO.
18.32 Zap PBBS on Next Mail Beacon
This parameter causes LAN-LINK to Zap your local PBBS next time
it beacons with a list of calls for which it has Mail.
18.33 PBBS Zap, Don't Disconnect After Sequence
This parameter stops LAN-LINK from issuing the automatic
disconnect when the Zap sequence is over. You can set it during
the Zap sequence. Use it to stop the disconnect if the sequence
gets out of sync with the messages, or if there is something
interesting you wish to do to the PBBS. This parameter resets
when the Zap sequence terminates.
18.34 Control Send of LAN-LINK.OUT
THe LAN-LINK.OUT file is a file that you can configure LAN-LINK
to transmit to an incoming connect (packet, AMTOR, Pactor and G-
TOR modes). Think of this file as a CTEXT File. If this flag is
set, the file will be transmitted. If this flag is OFF, the file
will not be transmitted. Use this file as a welcome or help file
to other stations when using LAN-LINK in a special event station.
19.0 Q Codes [NC/L]
This option displays help information about the use of the
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 96
Network Communications Language (NC/L) "Q" codes.
20.0 COMMUNICATIONS MODES
This menu allows you to change the communications mode of the
TNC. If your TNC hardware cannot support those modes, don't
bother to try them. This is software not hardware, and in spite
of what people tell you, software can't do everything. The commu-
nications modes shown in Figure 20 are available. Type in the
single letter to make your choice. While the KAM ports are set,
and the MFJ-1278 ports are defaulted in LAN-LINK (1 = VHF, 2 =
HF), don't forget that YOU HAVE to select the correct radio port
on the PK-232.
Figure 20 PK-232 Communications Mode Menu
V VHF PACKET
H HF PACKET
A AMTOR (STANDBY)
B BAUDOT (RTTY)
C MORSE (CW)
M AMTOR (MONITOR)
P PACTOR (STANDBY)
Q PACTOR (MONITOR)
S ASCII (RTTY)
N NAVTEX
G SIGNAL/G-TOR
X Manual
20.1 VHF PACKET
This is the 1200 baud VHF Packet Mode. LAN-LINK will optimize the
TNC link parameters for this mode.
20.2 HF PACKET
This is the 300 baud HF Packet Mode. LAN-LINK will optimize the
TNC link parameters for this Mode.
20.3 ASCII (RTTY)
This is the ASCII RTTY Mode. LAN-LINK will configure the TNC
parameters for this Mode at 110 baud.
20.4 BAUDOT (RTTY)
This is the BAUDOT RTTY Mode. LAN-LINK will configure the TNC
parameters for this Mode at 45 baud.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 97
20.5 MORSE (CW)
This is the CW Mode. LAN-LINK will configure the TNC parameters
for this Mode at the default CW speed (20 for the PK-232 and MFJ-
1278, 10 wpm for the KAM).
In this Mode the ALT-D Key will disengage the receive speed lock
inside the PK-232 to facilitate locking onto another signal and
Function Key 8 (F8) will turn the transmitter off.
LAN-LINK has a flag in the configuration file that lets you
configure the XMITOK parameter in the TNC. This flag allows you
to set XMITOK to "OFF" when you enter the CW communications mode,
and turn it "ON" again when you exit from the CW communications
mode.
20.6 AMTOR (STANDBY)
When you select the AMTOR Standby Mode you are placed into the
"Standby Receive" Mode. If you are in AMTOR Standby Mode, you
will not be able to display signals of the Chirpcopy Mode (which
means that you will not be able to display a QSO in progress).
The Alt-D Key and Function Key 8 (F8) both toggle between the
AMTOR STANDBY and MONITOR communications modes.
20.7 AMTOR (MONITOR)
If you want to read the mail on an existing AMTOR QSO in
progress, select the AMTOR (MONITOR) or Chirpcopy Mode.
The Alt-D key and Function key 8 (F8) both toggle between the
AMTOR STANDBY and MONITOR communications modes.
20.8 PACTOR (STANDBY)
When you select the Pactor Standby Mode you are placed into the
"Standby Receive" Mode. If you are in Pactor Standby Mode, you
will not be able to display signals from a QSO in progress.
The Alt-D Key and Function Key 8 (F8) both toggle between the
Pactor STANDBY and MONITOR communications modes.
20.9 PACTOR (MONITOR)
If you want to read the mail on an existing Pactor QSO in
progress, select the Pactor STANDBY or Chirpcopy Mode.
The Alt-D key and Function key 8 (F8) both toggle between the
Pactor MONITOR and STANDBY communications modes.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 98
20.10 SIGNAL
Use this option to select the PK-232 SIGNAL Mode. Read the PK-232
documentation carefully to understand how this mode works. Once
the PK-232 has identified the digital signal it is tuned to, use
the Communications Mode Select Menu a second time to select the
relevant mode and then set the baud rates and shift to display
the data if necessary.
20.11 NAVTEX
Use this option to select the NAVTEX Mode. Read the TNC
documentation carefully to understand how this Mode works.
20.12 G-TOR
If you are using a KAM, you may use this option to select the G-
TOR Mode. Read the TNC documentation carefully to understand how
this Mode works. If you are not using a KAM, this option will not
show up on your menu.
20.13 MANUAL
This option selects the HF logbook and copies the previous mode
entry in subsequent logging. Use this mode to log SSB or FM
contacts when monitoring the PacketCluster and working stations
spotted therein.
21.0 TERMINAL MODE MENU
This menu allows you to set the Terminal Configuration Mode. The
Terminal Menu provides different choices depending on which
communications mode you have selected.
21.1 Packet Terminal Menu
The Packet Terminal Mode of operation will be shown in the Status
window at the top of the screen. If you are reading the mail on a
station, the callsign of that station will be shown next to the
word "MAIL". If you are connected to someone, the call (and path)
will be shown prefixed by the "*>" sequence.
In the Packet Communications Mode, you are presented with the
choices shown in Figure 21.1. Type in the single letter to make
your choice.
21.1.1 Change Packet Baud Rate
In the PACKET Mode you may change the RF baud rate between 300,
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 99
600, 1200 and 2400 baud. While LAN-LINK allows these baud rates,
the TNC may not.
21.1.2 CQ/Beacons
In this Mode, you will see CQ and BEACON packets on the channel.
This Mode only works on the PK-232 and the KAM.
Figure 21.1 Packet Terminal Menu
B Change Packet Baud Rate
C CQ/Beacons
E Everything
I Information
L Turn MCON ON
M Read the Mail
O Turn Meta Beacon ON
S Just My Station (Solo)
T All Traffic
0 Multiple User Connects
F Turn Conference ON
21.1.3 Everything
You can set the TNC Mode to "Everything", i.e. show all packets
on the LAN.
21.1.4 Read the Mail
You can read the mail on a PBBS or other station and get
bulletins without connecting to that station yourself. You use
this Mode to do so. You will be prompted for the call whose
packets you wish to monitor. Remember to enter the call of the
station sending the packets, not the call of the one receiving
them. This mode only works without showing the packet headers on
the PK-232. On the other TNCs the headers will also be displayed.
You can also use this command to monitor both sides (read the
mail) on a QSO on a busy packet channel.
You may want to turn the Digipeat Data Display Mode off when
reading the mail.
21.1.5 Just My Station (Solo)
In this Mode, you will only see messages addressed to you. You
will only get messages from people who connect to you.
21.1.6 All Traffic
In this Mode you will see all of the data packet traffic on
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 100
channel. You can use this Mode to check that the TNC is working.
21.1.7 Information Packets
In this Mode you will see all of the packet traffic on channel
that contain information. You can use this Mode to check that the
TNC is working.
21.1.8 Single User Connects
This is the normal one-on-one Mode of operation (USERS 1).
21.1.9 Multiple User Connects
When you are in a Multiple Connect Mode, an asterisk will be
shown in the status window next to the word "PACKET". Each I/O
stream will show up in the Inwindow in a different color.
LAN-LINK supports two multiple connect modes, Individual and
Conference.
An extract of an actual "off the air" CRT display (showing
received text only) in a multi-user mode is shown below. Each
line of text as received by the TNC is prefixed (by the PK-232)
with the I/O channel number and callsign of the station its
connected with.
1:4X4IL: *** CONNECTED to 4X4IL via 4X4IC, 4X6JP
0:4X4IC: joe do u read?
2:4Z4ZB: *** CONNECTED to 4Z4ZB
1:4X4IL: Look for me on PR via 4X6JP 73s and Shalom.
2:4Z4ZB: GE JOE I WILL DIS THEN U CAN GO VIA THE REP>
1: *** DISCONNECTED: 4X4IL via 4X4IC, 4X6JP
0:4X4IC: UNPROTO CQ
2:4Z4ZB: GO AHEAD BOYS...DE ALON..>
0:4X4IC:
2: *** DISCONNECTED: 4Z4ZB
This is the normal Multi-connect Mode as described in the TNC
manual. Here you are connected to up to 10 stations and will send
different traffic to each of them. Each time you wish to send
something to a particular station, you must select the I/O
channel the station is connected on before typing the text or
sending the file.
The default stream change character for all TNCs in the VHF
multiple connect modes is "|" ($7C). In the KAM, it is "\" on HF
and "|" on VHF. They are both on the same key but one is in the
shift case. Be careful on HF as the "\" shows up in file
directories and confuses the computer. These values can be
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 101
customized. However to do so, they must be customized both in
LAN-LINK and in the TNC at the same time.
You select the I/O channel using the Alt-N key and moving the
cursor to the desired stream, or by typing the "|" character
followed by (in the TNC) the channel letter/number. For example
to do it manually, if you are connected to G8BTB on I/O channel 0
and to G3ZCZ on I/O channel 1, then to talk to G8BTB you would
type "|0" before any text, and similarly to send something to
G3ZCZ you would type a "|1" before the text you"re going to send
me. If you are not using a PK-232, read the TNC manual to deter-
mine if the I/O streams are identified by numbers or by letters.
The TNC2 standard configuration uses letters ("|A" etc.).
Use the Alt-N key and move the cursor up and down to select the
I/O channel automatically.
21.1.10 Conference
In the Conference Mode on the other hand, everything that you
type at the keyboard is automatically transmitted to each station
that you are connected with. Thus if you are linked to two
stations each line will be packeted twice by the TNC. You don't
have to worry about sending the wrong thing to the wrong person,
as they will all get the stuff.
You enter this Mode by selecting the "F" option in the Terminal
Menu. You terminate this Mode by selecting the "1" option.
You connect in the usual manner using Alt-C or the Connect Option
in the Call Menu. You must wait for a connection to be
established, or to time out, before attempting to connect to the
next station. If you do not, you will get an error message back
from the TNC.
In the Conference Mode, as the same text is transmitted on all
I/O channels, the throughput will be reduced. Slow down your
typing speed or use short packets. Should you check the link
status or call monitored list, you may not be able to get back
into the Converse Mode if you have too many packets outstanding.
If that happens, wait a while and then try to set the Converse
Mode with Function Key 10 (F10). You may have to try it a few
times, depending on how good your links are.
Don't try to send a file in the conference mode, it is not
designed for it. Keep the packets short (use short lines). Be
also warned that if you use the conference bridge on bad links
(such as crowded HF channels, or VHF/UHF channels with lots of
retries, the keyboard may seem to lock up. This is because LAN-
LINK has to wait for space to appear in the TNC buffer before it
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 102
can output the text.
The Conference Mode will only work in the PK-232 if DCDCONN is
set to ON. So if you are using a PK-232, LAN-LINK will do it for
you when you enter the Conference Terminal Mode in case you
forgot or/and haven't set the LAN-LINK.SYS file to include the
line "DCD ON". At the same time set LAN-LINK.SYS default states
to show the calls of other stations on each incoming line in the
Multiconnect modes (read the TNC manual on how to do this).
The Conference Mode will only work in the TNC2 if DCDCONN is
jumpered so that Pin 8 of the RS-232 Interface changes state when
you connect to someone else. If you get error messages and see
the characters "|J" on your screen, then the jumper probably
isn't set. The Conference Mode does not work on the TNC1.
In the Conference Mode, if any one of the stations disconnects,
the TNC will return to the Command Mode, and you must use
Function Key 10 (F10) to return to the Converse Mode before you
type another character of text.
21.1.10 Conference Bridge ON/OFF
This option toggles the Conference Bridge ON and OFF. In the
Bridge Multiconnect Mode you are acting as a central switch. You
can link together up to 10 stations in one multi-way connection.
In this Mode any packets arriving on any stream are echoed to all
other streams that you have "connects" on except the one that
they came in on. Anything you type will be sent to all connected
streams.
In this manner, all stations will not see their own text echoed
back. Each line of text output by LAN-LINK in this Mode will
contain the callsign of the station originating the packet. Your
packets will contain your call as entered in line 1 of the LAN-
LINK.SYS file. Thus for example, if your call was KB8RP/4X and
normally shows up in the packet header as KB8RP here it will show
in the data as KB8RP/4X.
Just remember that the Bridge puts out a lot of packets, so do
multi-way connects on a quiet frequency. You must be in the
Conference Mode to turn the bridge on, and any disconnect will
take the bridge down. Should that happen, toggle it on again. A
bridge will be shown in the status window whenever the Conference
Bridge is up.
21.1.11 Turn Metabeacon ON/OFF
This option lets you turn the LAN-LINK Metabeacon ON and OFF.
LAN-LINK provides you with a metabeacon, that gives you the
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 103
capability to transmit a long beacon message at periodic
intervals. The Metabeacon is loaded from the contents of one of
the LAN-LINK.00n files. These files may be created by the LAN-
LINK editor. When loading, LAN-LINK will insert a pass character
(^V) into the text before a carriage return, so as not to end the
packet before at least 240 characters, and not more than 255
characters have been output to the TNC. The maximum number of
characters that can be loaded into the Metabeacon is 1776. The
maximum number of packets in a Metabeacon is 7. You can also
force a hard carriage return or "end of packet" in the Metabeacon
by inserting the "\" (backslash) character, which will not be
transmitted, into the text.
The frequency of Metabeacon transmissions is the same as that of
the automatic CQ timer.
The MetaBeacon is designed for special event stations. PLEASE do
not abuse it.
21.2 AMTOR Terminal Menu
In the AMTOR Communications Mode, you are presented with the
choices shown in Figure 21.2. Type in the single letter to make
your choice.
Figure 21.2 AMTOR Menu
L Force LETTERS Case
K Turn SELCAL ON/OFF
R Set ROBOT/Mailbox
W CW Identification
Z Set ROBOT Infinite Delay
21.2.1 Force LETTERS Case
This option lets you force the PK-232 receiver to the letters
case if for some reason you appear to be in the numbers case. It
will return you to the Converse Mode.
If your TNC allows you to use a control character (^L) to force
the letters case, you don't need to go through all these menu
layers to do the job.
21.2.2 SELCAL ON/OFF
This command key toggles the SELCAL feature ON and OFF. When the
SELCAL is activated, as shown in the status window, the incoming
text from the TNC is scanned. When either the letters "ZCZC" or
"your callsign" (as entered in line 1 of the LAN- LINK.SYS file)
is received, the "capture-to-disk" is turned on. All subsequent
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 104
text will be stored in the LAN-LINK.RUN file until the letters
"NNNN" are received. At that time the "capture-to-disk" is turned
off.
21.2.3 Set ROBOT/Mailbox
This option lets you turn on the Mailbox during a regular AMTOR
QSO so that the other station can leave a message or download a
file remotely. You must only use it when the other station is
sending text.
21.2.4 CW Identification
This option only works on the PK-232, PK-900 and DSP 2232. You
use it to send a CW identification (CWID). The CWID is sent in
the FEC Mode. The CWID consists of the sequence "DE YOURCALLSIGN"
where YOURCALLSIGN is that entered into the PK-232 as "MYCALL".
You use this feature if your license requires you to identify in
Morse code as well as in the operating mode.
21.2.5 Set ROBOT Infinite Delay
You use this option to prevent the Robot from ever transmitting
when not linked. In the normal manner, the Robot counts down the
CQ delay parameter, and, when it gets down to 0, puts a CQ call
on the air. If the Infinite Delay is set, the CQ call will be
inhibited. This option thus puts the Robot into an indefinite
wait mode where it thinks it has sent out a CQ call and is
waiting for a reply.
You would use this Mode if you want to set up a MailBox on a
known frequency for some group or organization.
21.3 Baudot Terminal Menu
In the Baudot Communications Mode, you are presented with the
choices shown in Figure 21.3. Type in the single letter to make
your choice.
21.3.1 Set Baud Rate
This feature allows you to set a desired communications baud rate
directly. You will be prompted to enter the desired rate. Use
this command to avoid having to shift through too many intermedi-
ate states, if for example, you want to make a direct change from
45 to 100 baud.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 105
Figure 21.3 BAUDOT Menu
B Set Baud Rate
F Select Shift
N Turn NAVY MARS Message Protocol ON
U USOS OFF
K Turn SELCAL ON/OFF
W CW Identification
21.3.2 Select Shift
This feature lets you select Wide (850 Hz) or narrow (170 Hz)
shift directly. The PK-232 will copy 170 Hz signals using its
internal 200 Hz circuitry. If you have a KAM, you may also select
the Commercial Shift (425 Hz).
The shift is displayed in the status window at the top of the
screen. It is shown as "W"", "N" or "C" for wide, narrow or
commercial respectively.
21.3.3 NAVY MARS Message Protocol
The Navy MARS option toggles the Navy MARS Mode ON and OFF. When
the Navy MARS option is active, an "[N]" will be displayed in the
status window, and the feature performs the protocol described
below.
21.3.3.1: Any Carriage Return or Enter (CR) from the keyboard is
sent as CR, CR. (two sequential CR characters.
21.3.3.2: In a file transmission lines are terminated by a CR,
CR, LF (Line Feed) sequence.
21.3.3.3: In a file transmission, blank lines are sent as a LF
(without a CR).
21.3.3.4: In a file transmission, a plus sign "+" in the file is
replaced by a sequence of 12 "letters" characters.
There can be more than one + sign on a line.
21.3.3.5: In a file transmission, the sequence "NNNN" is trans-
mitted followed by a sequence of 12 "letters" charac-
ters. There can only be one "NNNN" sequence on a line.
21.3.4 USOS ON/OFF
This option toggles the Unshift on space (USOS) feature ON and
OFF. When the USOS is on, the TNC reverts to the letters shift
each time a "space" character is received. It helps when
displaying noisy copy.
If USOS is active, "USOS" will be shown in the status window at
the top of the screen.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 106
21.3.5 SELCAL ON/OFF
This command key toggles the SELCAL feature ON and OFF. When the
SELCAL is activated, as shown in the status window, the incoming
text from the TNC is scanned. When either the letters "ZCZC" or
"your callsign" (as entered in line 1 of the LAN-LINK.SYS file)
is received, the "capture-to-disk" is turned on. All subsequent
text will be stored in the LAN- LINK.RUN file until the letters
"NNNN" are received. At that time the "capture-to-disk" is turned
OFF.
You may use this feature when monitoring commercial RTTY
broadcasts to record news and other information, or when calling
CQ to start recording all incoming text and keep the QSO on disk.
You may use Function Key 1 (F1) to turn the capture to disk
permanently on to override the automatic turnoff if you wish.
21.3.6 CW Identification
This option is used to send a CW identification. You use this if
your license requires you to identify in Morse Code as well as in
the operating mode.
The identification consists of the sequence "DE YOURCALLSIGN"
where your callsign is that entered into the TNC as "MYCALL".
21.4 ASCII Terminal Menu
In the ASCII Communications Mode, you are presented with the
choices shown in Figure 21.4. Type in the single letter to make
your choice.
Figure 21.4 ASCII Menu
B Set Baud Rate
F Select Shift
K Turn SELCAL ON
W CW Identification
21.4.1 Set Baud Rate
This feature allows you to set a desired communications baud rate
directly. You will be prompted to enter the desired rate. Use
this command to avoid having to shift through too many intermedi-
ate states. For example, if you want to make a direct change from
110 to 1200 baud.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 107
21.4.2 Select Shift
This feature lets you select Wide (850 Hz) or narrow (170 Hz)
shift directly. The PK-232 will copy 170 Hz signals using its
internal 200 Hz circuitry. If you have a KAM, you may also select
the Commercial Shift (425 Hz).
The shift is displayed in the status window at the top of the
screen. It is shown as "W", "N" or "C" for wide, narrow or
commercial respectively.
21.4.3 SELCAL ON/OFF
This command key toggles the SELCAL feature ON and OFF. When the
SELCAL is activated, as shown in the status window, the incoming
text from the TNC is scanned. When either the letters "ZCZC" or
"YOURCALLSIGN" (as entered in line 1 of the LAN-LINK.SYS file) is
received, the "capture-to-disk" is turned on. All subsequent text
will be stored in the LAN-LINK.RUN disk file until the letters
"NNNN" are received. At that time the "capture-to-disk" is turned
off.
You may use Function Key 1 (F1) to turn the capture to disk
permanently on to override the automatic turnoff if you wish.
21.4.4 CW Identification
This option is used to send a CW identification. You use this if
your license requires you to identify in Morse code as well as in
the operating mode.
The identification consists of the sequence "DE YOURCALLSIGN"
where your callsign is that entered into the TNC as "MYCALL".
21.5 CW Menu
In the CW Communications Mode, you are presented with the Menu
shown in Figure 21.5. Type in the single letter to make your
choice.
Figure 21.5 CW Menu
L Lock to Receive Signal
S Set Morse Speed
U Unlock Morse Speed
X Turn XMITOK Flag ON
21.5.1 Lock to Receive Signal
This option locks the TNC to the speed of the incoming CW signal.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 108
21.5.2 Set Morse Speed
This option lets you set the CW speed.
21.5.3 Unlock Morse Speed
This option unlocks the TNC from the incoming CW signal. It
performs the same task as the Alt-D option keys. It is used to
speed up capture of a new signal or to break the lock when the
TNC appears to have locked up at the wrong speed.
21.6 Pactor Terminal Menu
Pactor applies to the KAM and PK-232 only, assuming they contain
Pactor firmware. In the Pactor Communications Mode, you are
presented with the choices shown in Figure 21.6. Type in the
single letter to make your choice. Do not use any of these
options when linked to another station or you may drop the link.
21.6.1 AUTO BAUD
This option configures the TNC to switch between 100 and 200 baud
on the HF Pactor link as determined by propagation Conditions.
Figure 21.6 Pactor Menu
0 AUTO BAUD
1 Force 100 BAUD
2 Force 200 BAUD
H Enable Huffman
K Disable Huffman
21.6.2 Force 100 Baud
This option forces the TNC to use 100 baud on the HF Pactor link
as determined by propagation Conditions.
21.6.3 Force 200 Baud
This option forces the TNC to use 200 baud on the HF Pactor link
as determined by propagation Conditions. This option is only
available for the KAM.
21.6.4 Enable Huffman
This option enables Huffman compression of the transmitted text.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 109
21.6.5 Disable Huffman
This option disables Huffman compression of the transmitted text.
22.0 EXIT TO DOS
When you exit the program and return to DOS, if the Shut down
(QRT) flag is set to 0, the TNC is put into the VHF default mode
in which it rejects calls from any other stations. (Read about
the CFROM and/or CONOK command in the TNC manual). You can, if
you wish, leave the TNC powered, and, if you also leave the VHF
radio powered up, you will be active as a digipeater, but at the
same time anyone trying to connect with you will receive a "busy
signal". The MBX command (Reading the Mail) is also cleared at
this time.
If you want to leave the TNC set up to accept messages when LAN-
LINK is not active, customize the shut down state as described in
the Section 18.23.
23.0 THE ELMER MENU
ELMER is a smart server or second operator feature described in
Appendix 7. The ELMER Menu presents you with the choices shown in
Figure 23. Type in the single letter to make your choice.
Figure 23 The ELMER Menu
C Change ELMER File
E Turn ELMER ON/OFF
L Load ELMER.QSO
P Pick File to edit
S Edit ELMER.QSO
T show state Table
23.1 Change ELMER File
This option allows you to change the ELMER state table file.
23.2 Turn ELMER ON/OFF
This option allows you to turn ELMER ON and OFF. If the ELMER
state table file (ELMER.QSO) is not present, you will not be able
to activate ELMER.
23.3 Load State Table (ELMER.QSO)
This option allows you to reload the state table. The name of the
state table will appear in the menu.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 110
23.4 Pick File to Edit
This option allows you to pick and edit, a file with the default
filetype of "TXT".
23.5 Edit State Table (ELMER.QSO)
This option allows you to edit the state table.
23.6 Show State Table
This option allows you to see the contents of the state machine.
It is used in debugging the logic to ensure that the contents of
the table match what you thought you put into it. A typical set
of contents appears as shown in Figure 23.1. The keywords have
been capitalized and set to 15 characters wide. None existent
characters have been represented as periods.
Figure 23.1 Typical ELMER State Table
L C N R E KEYWORD U FILE
0 1 2 0 0 WHAT........... 0 *
1 2 3 0 0 ENGLISHMAN..... 0 *
2 2 100 0 0 SYSTEMS........ 0 *
3 3 4 0 0 DOING.......... 0 *
4 4 1 0 0 COUNTRY........ 0 ME-USA.TXT
5 1 1 0 0 EQUIPMENT...... 0 PK232COM.TXT
24.0 RADIO MENU
The Radio Menu provides you with the capability to exercise the
interface to a Kenwood Radio. The options available are shown in
Figure 24-1. Type the single letter to make your choice. All
commands will be ignored if the radio is not enabled. The radio
interface is automatically enabled at LAN-LINK initialization
time.
Figure 24-1 The Kenwood Radio Menu
F Select VFO A/B
M Set Mode
Q Turn Flag QSY ON/OFF or N/A
R Read VFO A Frequency
S Set Frequency
V Speak Frequency
24.1 Select VFO A/B
This option sets the VFO that will be interrogated or set by LAN-
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 2 Page 111
LINK.
24.2 Set Mode
This option sets the radio mode (USB, LSB, FM, CW etc.). You will
be prompted to supply the mode.
24.3 Turn Flag QSY ON/OFF or N/A
This option set the QSY Flag as follows:
N/A Radio is not enabled.
ON QSY to the frequency of a DX Alert (if in PacketCluster
mode).
OFF Don't QSY in response to a DX Alert.
24.4 Read VFO Frequency
This option reads and displays the frequency of the selected VFO.
24.5 Set VFO Frequency
This option sets the frequency of the selected VFO. You will be
prompted to supply the frequency.
24.6 Speak Frequency
This option sends a command to the radio to announce the
frequency of the selected VFO. If the radio is equipped with a
voice annunciator the radio will announce the frequency. If the
radio is not equipped in such a manner, the command will be
ignored.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 112
Appendix 3 LAN-LINK Disk Files
The following disk files are associated with the LAN-LINK
program.
LAN-LINK.COM
LAN-LINK.SYS
*.RUN
LAN-LINK.LOG
LAN-LINK.DIR
CONFIG.SYS
*.MBX
*.BBS
LAN-LINK.001 .. LAN-LINK.010
QBU-RX.BAT
QBU-TX.BAT
LAN-LINK.QTA
QZ*.BAT
ELMER.QSO
LAN-LINK.OUT
*.DMO
The "*" represents a "wildcard" character in the manner of DOS.
Consider each file in turn.
1.0 LAN-LINK.EXE
This is the program. You activate it from DOS by typing the word
"LAN-LINK" followed by "ENTER" in the normal manner of invoking
DOS commands.
2.0 LAN-LINK.SYS
This file contains the configuration information for both the
program and the TNC. Use the customization options in the
parameters menu to make any changes not taken care of in the
INSTALL program.
The contents of the default file together with an item (line)
number are shown below.
1. Callsign
2. Selcal
3. CQ Text
4. CTEXT Line
5. ELMER Flag
6. CQ Delay (seconds)
7. CQ Delay (minutes)
8. :QSP: Message Relay Flag
9. PC Serial Communications Port Number
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 113
10. TNC Type
11. PC to TNC Baud Rate
12. VHF Log Book File
13. HF Log Book File
14. GMT Offset
15. Path Directory File name
16. Brag Tape File name
17. PBBS Snatch Mail Trigger Word
18. QTC Snatch Flag
19. PBBS Snatch Flag
20. Shut Down Mode (QRT Flag)
21. PC to TNC Data Bits
22. PC to TNC Parity Bit
23. PC to TNC Stop Bits
24. DCD Flag
25. QBM Download Sub-directory
26. Run File Directory Path
27. PBBS Read Request Command
28. Local PBBS Callsign
29. SAREX Callsign
30. SAREX Capture to Disk File name
31. PacketCluster Call
32. TNC Specific Parameters
33. Node Drop Link Flag
34. Sound Flag
35. Display Computer Generated Commands Flag
36. Date/timestamp in Call Sequence Flag
37. Keyboard Character Beep value (number of characters).
38. :QBU: Receiving Station Batch file (QBU-RX.BAT)
39. :QBU: Originating Station Batch file (QBU-TX.BAT)
40. Capture-to-disk Flag
41. Beacon Control/LAN-LINK handshake Flag
42. Read Bulletin Character
43. PBBS Subject String
44. PBBS Message String
45. VHF Paclen
46. HF Paclen
47. Beacon Time
48. Number of CQ Lines
49. Word wrap
50. PC Port 4 Custom Address
51. PC Port 4 Custom IRQ
52. VHF Stream switch character
53. HF Stream switch character
54. TNC Error message
55. Connect Timeout Delay
56. Custom Prompt
57. ELMER Configuration File
58. Expand Transmitted File flag
59. Input Message Base Count
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 114
60. Default users
61-88. Custom Colors
89. First PacketCluster Command
90. Second PacketCluster Command
91. TNC Mailbox ON Command
92. TNC Mailbox OFF Command
93. VHF Maxframe Command
94. HF Maxframe Command
95. Inhibit VHF Logging Flag
96. Inhibit HF Logging Flag
97. Printer Permanent Flag
98. Log Disk Update Flag
99. Secondary Log Flag
100. Auto Answer Flag
101. RUN File Disk Update Flag
102. Default CW Speed
103. Secondary Logbook
104. BBS List Command
105. BBS List Mine Command
106. BBS Custom Command
107. BBS Bye Command
108. Start Up Packet Terminal Mode
109. Page Time (:QIC: Seconds)
110. Packet Cluster DX Alert Tone CW Dit time
111. Packet Cluster DX Alert Tone CW Note
112. Packet Cluster DX Alert Mode
113. Mode File Flag
114. BAUDOT Color Change Text String
115. Default RTTY Baud Rate
116. Dual Window Flag
117. TNC String for Modem 9600 baud packet
118. TNC String for Modem 1200 baud packet
119. TNC String for Modem RTTY
120. TNC String for Modem 300 baud packet
121. TNC String for Modem RTTY and 1200 baud packet
122. TNC String for Modem 300 baud and 1200 baud packet
123. TNC String for Modem Fuji
124. Delay after a command line
125. Radio
126. Radio Port
127. Radio Port baud rate
128. Radio Port Bits
129. Radio Port Stop Bits
130. Radio Port Parity
131. Radio Address
132. Flag QSY
133. Flag DX Alert Prefix Check
134. start of band parameters for DX Alert message log search
135. * end of band parameters; modes for DX Alert message log
search
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 115
136. Start of Scan Words (MUST HAVE AT LEAST ONE)
137. * end of Scan Words
138. Start of Common Calls (MUST HAVE AT LEAST ONE)
139. * end of Common Calls
140. Remaining TNC start up Commands.
The contents of each line are described in the section of the
Parameters menu which deals with customizing them. The others,
described below, can only be changed by using the Editor. The
remaining lines contain commands to the TNC. For further informa-
tion about them refer to the TNC manual. LAN-LINK assumes
different defaults (in some instances) to those set in the TNC.
The LAN-LINK.SYS file contains only those that are different to
the TNC default reset state.
2.1 CTEXT Line
This parameter is the CTEXT line changed in the TNC Menu.
2.2 ELMER Flag
This parameter is the ELMER Flag. If it is a "1", ELMER is primed
for activity. ELMER is only active in the Packet communications
mode, when you are connected to another station. If the ELMER
flag is a "0", or the ELMER state table file is not present in
the default directory, LAN-LINK will never activate ELMER.
2.3 PC Port 4 Custom Address
This parameter is the decimal value of the address of your Port
4. Use this parameter if you are using a non standard Serial I/O
card. Configure the PC Port to 4. The PC default address for Com4
is 2E8 (hex) or 744 (decimal).
2.4 PC Port 4 Custom IRQ
This parameter is the decimal value of the IRQ of your Port 4.
Use this parameter if you are using a non standard Serial I/O
card. Configure the PC Port to 4. The PC default IRQ for Com4 is
3.
2.5 VHF Stream Switch Character
This parameter is the VHF stream switch character. If you wish to
change it, you must enter the ASCII representation in this line,
and the equivalent stream switch command in the LAN-LINK.SYS
file.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 116
2.6 HF Stream Switch Character
This parameter is the HF stream switch character. If you wish to
change it, you must enter the ASCII representation in this line,
and the equivalent stream switch command in the LAN-LINK.SYS
file. The KAM is currently the only TNC that has different HF and
VHF stream switch characters.
2.7 TNC Error Message
This parameter is the error message your TNC generates. The PK-
232 generates "?What?". Others may generate "EV?" or "?EH".
2.8 Connect Timeout Delay
This parameter is the time, in minutes, LAN-LINK lets you stay
connected to another packet station, after the receipt of the
last incoming character.
2.9 ELMER Configuration File
This parameter is the name of the default ELMER Configuration
file. It is changed through the ELMER Menu.
2.10 Expand Transmitted Files Flag
The Flag tells LAN-LINK to scan the outgoing text when a file is
transmitted and perform the same conversions it does to the
contest text. You can insert the '##', "#1' and "#T" parameters
in the files to transmit, your call sign, the other station's
call, and the time of day. Set this parameter to 1 to enable the
feature, 0 to disable it.
2.11 First PacketCluster Command
This parameter is the first command (up to 20 characters) LAN-
LINK sends to the PacketCluster after receiving a ">" character
at the end of line from the PacketCluster.
2.12 Second PacketCluster Command
This parameter is the second command (up to 20 characters) LAN-
LINK sends to the PacketCluster after receiving a ">" character
at the end of line from the PacketCluster.
2.13 TNC Mailbox ON Command
This parameter is the command (up to 15 characters) your TNC
expects to turn its internal mailbox ON.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 117
2.14 TNC Mailbox OFF Command
This parameter is the command (up to 15 characters) your TNC
expects to turn its internal mailbox OFF.
2.15 VHF Maxframe Command
This parameter is the command (up to 15 characters) your TNC
expects to set the VHF MAXFRAME parameter.
2.16 HF Maxframe Command
This parameter is the command (up to 15 characters) your TNC
expects to set the HF MAXFRAME parameter.
2.17 Inhibit VHF Logging Flag
When set to 1, automatic VHF Logging is disabled.
2.18 Inhibit HF Logging Flag
When set to 1, automatic HF Logging is disabled.
2.19 Printer Permanent Flag
When clear (set to 0), if you leave the printer on during a
packet connect, it will stop printing when you disconnect. This
stops the printer generating lots of garbage. If you set this
parameter to 1, the printer will not stop printing when you
disconnect.
2.20 Log Disk Update Flag
If this flag is set to 1, LAN-LINK writes each log entry to disk
as you enter it. If this flag is not set (=0), LAN-LINK writes
the log entry to a buffer and updates the disk when the program
is terminated. Set the flag ON to ensure that rare DX contact is
logged, Set it OFF for speed, or if power dropouts are not a
problem in your area.
2.21 Secondary Log Flag
If this Flag is set to 1, LAN-LINK allows you to search both the
current log book and a secondary logbook for the call of a
station.
2.22 Auto Answer Flag
If this flag is set to 1, AND you have a LAN-LINK.OUT file on
your system, LAN-LINK will transmit the contents of the LAN-
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 118
LINK.OUT file to every incoming connection.
2.23 Ctdsk File Disk Update Flag
If this flag is set to 1, LAN-LINK will close the capture-to-disk
file (YYMMDD.RUN) between received messages. If the flag is not
set, LAN-LINK will close the file when all messages have been
received, or a DISCONNECT takes place.
2.24 Default CW Speed
This is the default CW speed for the multi-mode TNC (KAM, PK-232
or MFJ1278).
2.25 Secondary Logbook
This is the name of the secondary logbook.
2.26 BBS List Command
This is the BBS List Command. The default value is 'L'.
2.27 BBS List Mine Command
This is the BBS List Mine Command. The default value is 'LM'.
2.28 BBS Custom Command
This is a configurable BBS List Command. The default value is
'KM'.
2.29 BBS Bye Command
This is the BBS Bye Command. Change this parameter when the
default 'B' command only drops you to the Node.
2.30 Start Up Packet Terminal Mode
This is the Packet Terminal Mode when LAN-LINK is first
activated. Set this to the letter corresponding to the terminal
mode you like being in. See Section 21.1. Use the corresponding
letter, as shown in Table 2.30.
Table 2.30 Start Up Terminal Mode
Letter Mode Actions
I INFO lets you only see packets containing information.
S SOLO lets you only see messages addressed to you.
C CQ/B lets you see beacons and CQ calls as well.
T TRFC lets you see packets containing messages as well.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 119
E EVRY lets you see everything on channel, including the
link control packets.
2.31 Page Time (:QIC: Seconds)
This is the number of seconds the system pages the operator in
response to a QIC command, if the sound is turned on.
2.32 PacketCluster DX Alert Tone CW Dit time
This is the time period for 1 dit sound in the PacketCluster
audible DX alert message.
2.33 Packet Cluster DX Alert Tone CW Note
This is the tone for the PacketCluster audible DX alert message.
2.34 Mode File Flag
If this flag is set, LAN-LINK will change the name of the LAN-
LINK.001 to LAN-LINK.010 when you change communications modes.
The name will change to the mode followed by a number, i.e.
BAUDOT.001 to BAUDOT.002, or AMTOR.001 to AMTOR.002.
2.35 BAUDOT Color Change Text String
This is a pair of characters that LAN-LINK will scan text
appearing in the incoming window for. When LAN-LINK recognizes
the pair, it will change colors. This parameter is customizable
to allow you to override apparent random changes of color, since
there is no agreed standard way for signaling 'over' in BAUDOT.
2.36 Dual Window Flag
This flag applies to the PK-900 and DSP 2232 only. If this flag
is set, LAN-LINK separates out the text streams coming from each
port and directs them to two separate windows. If the flag is
reset, the text streams are combined into a single incoming
window.
2.37 TNC String for Modem 9600 baud
This item applies to the PK-900 and DSP 2232 only. This is the
command used to select the modem for working 9600 baud packet.
2.38 TNC String for Modem 1200 baud
This item applies to the PK-900 and DSP 2232 only. This is the
command used to select the modem for working 1200 baud packet.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 120
2.39 TNC String for Modem RTTY
This item applies to the PK-900 and DSP 2232 only. This is the
command used to select the modem for working HF RTTY.
2.40 TNC String for Modem 300 baud
This item applies to the PK-900 and DSP 2232 only. This is the
command used to select the modem for working 300 baud HF packet.
2.41 TNC String for Modem RTTY and 1200 baud
This item applies to the PK-900 and DSP 2232 only. This is the
command used to select the modem for working simultaneous HF RTTY
and VHF 1200 baud packet.
2.42 TNC String for Modem 300 baud and 1200 baud
This item applies to the PK-900 and DSP 2232 only. This is the
command used to select the modem for simultaneous HF 300 baud
packet and 1200 baud VHF packet.
2.43 TNC String for Modem Fuji
This item applies to the PK-900 and DSP 2232 only. This is the
command used to select the modem for working Fuji 1200 baud PSK
packet.
2.44 Delay after a command line
This item is the number of milliseconds to wait between sending
lines to the TNC output buffer.
2.45 Radio
This item is the name of the Radio. Kenwood has been tested, Icom
may work (coded but not tested). If this is not set to Kenwood or
Icom, the Radio functions are disabled.
2.46 Radio Port
This item is the serial port for the Radio (1 to 4). If set to 0,
the Radio functions are disabled.
2.47 Radio Port baud rate
This item is the serial port baud rate for the Radio. Check the
correct value in the Radio manual.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 121
2.48 Radio Port Bits
This item is the number of data bits on the serial port for the
Radio. Check the correct value in the Radio manual.
2.49 Radio Port Stop Bits
This item is the number of stop bits on the serial port for the
Radio. Check the correct value in the Radio manual.
2.50 Radio Port Parity
This item is the parity value on the serial port for the Radio.
Check the correct value in the Radio manual.
2.51 Radio Address
This item is ignored for Kenwood radios. For Icom, it is the
decimal value of the radio address. Check the correct value in
the Radio manual.
2.52 Flag QSY
This flag determines of LAN-LINK tunes the radio to the frequency
of the PacketCluster DX Alert message automatically.
2.53 Flag DX Alert Prefix Check
This flag determines how LAN-LINK responds to a DX Alert message.
If the flag is set, LAN-LINK checks to see of the prefix is in
the log.
2.54 Band parameters for DX Alert message log search
These lines contain the band, reference frequency (Hz), low and
high band search flags. They can be changed via the Radio Menu.
Typical values are:
10, 28300000.0,Y,Y
12, 24930000.0,Y,N
15, 21200000.0,Y,Y
17, 18110000.0,Y,Y
LAN-LINK checks the frequency of the DX Alert message to see if
it matches on in these lines. If it does, then LAN-LINK compares
the frequency with the value on the corresponding line to
determine if the DX Alert frequency is higher or lower than the
reference frequency.
If the frequency is lower than the reference, and the low band
search flag is "Y", LAN-LINK will check to logbook to see if the
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 122
prefix is in the log.
Similarly, if the frequency is higher than the reference, and the
high band search flag is "Y", LAN-LINK will check to logbook to
see if the prefix is in the log.
If LAN-LINK does not find a match, the check mark is displayed.
2.55 Modes for DX Alert message log search
This line marks the end of the band parameters for DX Alert
message log search with the *. It then contains the
communications modes corresponding to the low and the high parts
of the band. Typical values are:
*,CW,SSB
2.56 TNC Parameters
The remaining lines contain parameters loaded into the TNC at
initialization.
If you are not using a TNC1 you MUST set the HEADERLN parameter
to ON. The packet headers and the text of the packets must show
up on your screen on separate lines. You must also have the "Echo
as Sent" feature set ON ("EAS ON" for PK-232 and "XM" ON " for
the KAM).
3.0 *.RUN
These files contain incoming data from the TNC recorded while the
"capture-to-disk" function was active. LAN-LINK names them as
YYMMDD.RUN automatically (YY = Year, MM = Month, DD = Date, i.e.
920903.RUN is a file for 3 Sept 1992).
4.0 *.DBF (HF.DBF and VHF.DBF)
These file contain the log entries. They are Dbase 3 and 4
compatible. The format of the logbook file is the same as that
used by the LOGBOOK package of the PC-HAM software package, with
a little additional space for comments.
5.0 LAN-LINK.DIR
This is the directory file as described in Appendix 2, Section
6.1.2. You use it to store names, handles, NET/ROM, TheNet, KA-
Node, ROSE or digipeat paths as well as name/callsign relation-
ships. Sample lines are shown below.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 123
Joe G3ZCZ
Alon 4Z4ZB V 4X6AA
Milt 4X6AA
LR 4X6LR
hf-il 4x4hf v 4z4zb 4x4il
hf-rj 4x4hf v 4z4zb 4z4rj
K1HTV ELK v WB4APR-5! SNJ3! NNJ! WMA! SCCT!K1HTV
w9tnn-2 jrw !% w3eax-7 !& w9tnn-2
You create this file with the Editor or by using your word
processor in its non-document mode. You must leave at least one
space character between the first (key) word and the connect
path. When you type in the key word, the program does not care
about upper or lower case.
You may also use the "reMember Path" option in the Call Menu to
make entries in this file.
If you already have a YAPP.DIR or a PK232COM.DIR file just rename
it to LAN-LINK.DIR and add any NET/ROM and/or KA-Node paths.
All path entries in LAN-LINK.DIR must be on a single 80 column
line.
6.0 CONFIG.SYS
You must have a CONFIG.SYS file on the boot disk if you are going
to use the disk logging features. This file must contain the line
FILES = 20.
See the DOS manual for more information about the CONFIG.SYS
file.
7.0 *.MBX
These are the files associated with the stations you have
designated as LAN store and forward mailboxes. Other stations can
only :QRU: with you if you have designated them as QRU stations
and have a "CALLSIGN.MBX" file on your disk. For example, if you
want to use 4Z4ZB as a store and forward mailbox, you will have
to create an ASCII file called 4Z4ZB.MBX using Editor, or the
non-document mode of your word processor. In this file you will
put a list of the call signs of the stations 4Z4ZB can connect
with reliably. For example, if you want 4Z4ZB to be able to store
messages from you to 4X6AA, 4X6LR, G3ZCZ, ON8IK, F0WN,and G8BTB,
you would put those call signs in the file, one call on a line as
follows.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 124
4X6AA
4X6LR
G3ZCZ
ON8IK
F0WN
G8BTB
When the QRU function is invoked either by you manually or by
4Z4ZB connecting to you and sending you the command :QRU:, any
message files present on your system addressed to any of those
stations (E.G. G3ZCZ.OUT and ON8IK.OUT) will be transferred from
you to 4Z4ZB just as if you had tried to :QSP: the messages
manually or as if G3ZCZ or ON8IK had connected directly to you.
The file names on your system will be changed to *.OLD.
You must create one file for each designated store and forward
station, i.e. 4Z4ZB.MBX, G3ZCZ.MBX etc.
8.0 *.BBS
These are LOCAL-BBS.BBS AUTO-Upload Command files. Each file is
named for the callsign of the BBS that you wish to access. It
must have exactly the name as the callsign of the BBS. If the BBS
is W9TNN-1 the name of the file must be W9TNN-1.BBS, or if the
BBS is 4Z4ZB then the file must be called 4Z4ZB.BBS. The file
must be an ASCII file. that means the word processor must be used
in the non-document mode to create it.
This file contains the command sequence that you would have typed
at the keyboard if you were accessing the BBS manually. The ONE
difference is that the text of a message you are uploading with
the S command must be followed by the character strings ":EOF:"
or "/EX" (on a separate line) as illustrated by the example
below.
If you use the "D" command to download a text file, the file will
end up in a separate file on your disk ONLY IF a file of the same
name does not exist on your drive.
Do delete "read" mail from your local PBBS. Don't clutter the
PBBS's disk with your read mail. The "LM" command is built into
LAN-LINK to remind you of what you have out there.
The PBBS "S" command (including its variations such as "SP") is
the only multiple line command allowed. You can put all the
single line commands such as "D", "H", "?", "L", and "R" in the
PBBS.BBS file.
A "multiple command" is defined in this instance as a command
which allows you to enter multiple lines before the PBBS will
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 125
send back a ">" character (i.e. one that the PBBS tells you to
type in text and terminate it with the Control-Z (^Z) character).
A typical message could be as shown below.
SP G3ZCZ @ N4QQ
LAN-LINK
I think it is great. However, why don't you change the
following...... (add your comments here).
73 de your name
:EOF: {last line may also be "/EX"}
k 1234
d \net\lan-link.doc
s g8btb
Test Message
This is a test message.
:EOF:
lm
r 567
r 593
9.0 LAN-LINK.001 - LAN-LINK.010
These are 10 different text files with fixed names. They can be
transmitted using the Alternate function keys. Their contents can
be viewed using the Shift function keys. In all cases the
function key to use for a particular file corresponds to the
number in the file suffix. For example, use Alt/Shift Function
Key 3 (Alt-F3) to transmit/view file LAN-LINK.003. You may also
use the Edit Menu to edit and/or create the files.
In case you forget what you put in each of the files, LAN- LINK
allows you to take a peek into all of them at the same time. Use
Control Function key 1 (Control-F1) to look at the first line of
all the LAN-LINK.001 - LAN-LINK.010 files and the Brag Tape.
If the Mode File flag is set, LAN-LINK changes the files as you
change modes. You thus have 10 files in EACH mode, accessible via
the same set of control function keys. The file names are shown
below.
COMMUNICATIONS MODE Mode Flag FILE NAMES
All OFF LAN-LINK.001 to LAN-LINK.010
Packet ON LAN-LINK.001 to LAN-LINK.010
AMTOR ON AMTOR.001 to AMTOR.010
BAUDOT ON BAUDOT.001 to BAUDOT.010
ASCII ON ASCII.001 to ASCII.010
CW ON MORSE.001 to MORSE.010
Pactor ON PACTOR.001 to PACTOR.010
G-TOR ON G-TOR.001 to G-TOR.010
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 126
10.0 QBU-RX.BAT
This is the command or batch file used in the :QBU: originating
station.
11.0 QBU-TX.BAT
This is the command or batch file used in the :QBU: receiving
station.
12.0 LAN-LINK.QTA
You can leave a message on your system for someone else in a file
named CALLSIGN.OUT. When the station with that callsign connects
to you, the message will be sent, and the filename will be
changed from CALLSIGN.OUT to CALLSIGN.OLD. This is fine as long
as the path between the stations good. If the path is marginal,
it is possible that your station will transmit the message and
change the filename, but the link will drop out before the
message is received at the other station. If the other station
does not connect to you and :QSM:, the message may get lost. If
this situation occurs, you can tell LAN-LINK that there is a bad
path between you and that station, and not to change the file
names without an explicit :QTA: instruction from that other
station. You do this by putting the call of the station(s) having
a bad path in an ASCII file called LAN-LINK.QTA. Put one call on
each line in the form
N9BE
G8BTB
You must use the root call of the station without an SSID. that
means, if the station is N9BE-4, just put N9BE in the file.
LAN-LINK will automatically acknowledge incoming messages from
stations with callsigns in the LAN-LINK.QTA file with a ":QTA:".
13.0 QZ*.BAT
As any LAN-LINK station can either receive or originate a :QZD:
and a :QZU: command, LAN-LINK uses four batch files to control
Zmodem transfers. These files are as follows.
QZU-RX.BAT Batch file implemented after receipt of :QZU:
QZU-TX.BAT Batch file implemented after transmission of :QZU:
QZD-RX.BAT Batch file implemented after receipt of :QZD:
QZD-TX.BAT Batch file implemented after transmission of :QZD:
Each LAN-LINK user must configure the QZ*.BAT files for their
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 3 Page 127
systems. The port number in the batch file should be set to the
PC I/O Port used. The data rate in the batch file should be set
to the data rate used between the PC and the TNC, NOT the data
rate used on the radio link.
For example, the default QZU-RX.BAT file of
"pcz 1 1200 rz %1" should be changed to
"pcz 2 1200 rz %1" if you are have interfaced your TNC to Port
2 on your PC. If, the baud rate between the TNC is 2400 baud, the
file should be changed to "pcz 2 2400 rz %1".
Each of the four batch files have to be customized for each user
who is not using PC Port Com1 and 1200 baud between the PC and
their TNC. The INSTALL program takes care of that chore. The high
level of customization required here is because different Zmodem
implementations require different sequences of instructions and
LAN-LINK does not want to limit you to a specific one.
14.0 ELMER.QSO
This is the state table (configuration file) for ELMER. The
contents of the file are as described in Appendix 8. If this file
is not present in the same sub-directory as LAN-LINK, you will
not be able to activate ELMER.
15.0 LAN-LINK.OUT
This file will be transmitted to all incoming connects (except
when in the multi user mode), if the file is present, and if the
Auto Answer flag is enabled. You can think of this file as a
CTEXT File.
16.0 *.DMO
These files are demonstration or test files. When LAN-LINK is put
into the Demo Mode (LAN-LINK Menu), LAN-LINK treats the lines of
text read from these files as if they came in from the TNC via
the serial port. Use these files for demonstrations and/or tests
of different features.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 4 Page 128
Appendix 4 Local Area Network Capability
VHF Packet radio systems can be considered as part of a Local
Area Network (LAN) in which messages can be left by one station
in the computer belonging to a second station. At HF the same is
true, but the area becomes greater. The basic problem here is
that people can only send and receive messages to or from you
when you are on-line. To compensate for this, BBS stations were
developed which allowed both messages and bulletins to be stored
by anyone for later retrieval.
LAN-LINK allows you to store messages in your computer so as to
use it as an automatic answering machine. By storing the messages
in a file called by the name of callsign, with the file extension
".OUT", anyone connecting to the computer will get their message
without having to request it. LAN-LINK also extends that concept
to cover the eventuality of you wanting to take your computer
off-line for some reason. You may now load the message into any
other computer you can connect to using elements of the Q code
adapted to the High Level Network Communications Language (NC/L)
first proposed in my book Software for Amateur Radio, (Book
number 1560) published by TAB Books, Blue Ridge Summit, Pa. 17214
U.S.A.
1.0 LAN Protocol (G3ZCZ Version)
The protocol is as follows. When connected to someone who has
their LAN-LINK configured as a host, if you want to store a
message on that system, you use "QSP". You send the other station
":QSP: CALLSIGN" where "CALLSIGN" is the callsign of the station
that the message is for, not the callsign of the host station in
whose computer you are storing the message. [Note use only one
space character after the :QSP:].
For example if you want to store a message for 4Z4ZB in 4X6AA's
computer which is configured as a LAN-LINK Store and Forward
system, you would first connect to 4X6AA and then send the
command as ":QSP: 4Z4ZB". Better still use :QSP: option in the
Lan-Link Menu to automate the sequence.
The computer at 4X6AA will respond either with a statement saying
that it is ready for you to go ahead, or send a message saying
that it can't comply. If it is ready you get a positive reply
which will take the form :QRV: CALLSIGN which if you know the Q
code, means "I am ready to accept a message for CALLSIGN".
At this time you may go ahead and send the message. If you type
the message at the keyboard, you may use either a Control-Z (^Z)
character or the character sequence ":EOF:" followed by a
carriage return (the "Enter" key) to terminate the message. If
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 4 Page 129
you have first written the message into a text file you may then
send it using the "Send File" option of the Files Menu and the
termination sequence is automatic.
Once you have completed the message, the other (host) computer
will either reply that the message has been successfully stored
or give you an error message.
If the message is stored and ready to be sent next time the
addressee connects to that computer, you will see the message
:QSL: on your screen. If something went wrong, you will get back
a negative message taking the form :QNO: followed by a number.
The number tells you why the operation failed.
2.0 Message Format
The message is stored just as if you had left it in your system
(except that a header is added identifying the time of reception
and the call of the sending station). It will contain a header
showing the date and time it was received and your callsign.
Should a message for that station already be in the system, yours
will be appended to it. In the event your upload is aborted, the
amount of text received before the abort occurred will be stored
as the message.
When you disconnect from the other LAN-LINK host station, its
mail beacon will be updated.
Once the message is loaded in the host, it can only be deleted by
the operator of the host station. When the addressee connects to
the host and receives the message, the file type will change from
".OUT" to ".OLD". Note QTA stations require positive confirmation
of receipt of message for the renaming to take place.
3.0 ASCII File Uploading/Downloading
There comes a time when you want to leave a file on your system
for someone to download later. You can do this by using NC/L to
control the transfer. You must leave the file in the file
download sub-directory defined in the LAN-LINK.SYS FILE (default
value is C:\LAN-LINK\FILES). You must first create the sub-
directory, if it does not exist. The station who wants the
message then asks for it using :QBM: FILENAME.TYP. They do not
need to use the full sub-directory path. They must, however,
leave a single space character between :QBM: and the filename. In
AMTOR the Mailbox must be turned on for remote functions.
For example, you have the latest ARRL DX bulletin, and you want
to pass it on. You could pass it to selected people by copying
the file to individual messages with the filetype ".OUT", e.g.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 4 Page 130
4X6AA.OUT, 4Z4ZB.OUT or even G3ZCZ.OUT if you want me to get it,
which wastes a lot of disk space.
On the other hand you could tell people that the file was
available for downloading, either in the CTEXT connect message
line which everyone gets when connecting to you by configuring
LAN-LINK accordingly, or in individual (".OUT") messages.
If you include the following in your CTEXT message
"ARRLDX.015 now available"
people will know that to download it, they just have to type the
line ":QBM: ARRLDX.015" (one space character between :QBM: and
the file name) to get the file. LAN-LINK is not designed as a
BBS, however, if you copy the contents of the \LAN-LINK\FILES
sub-directory into a file called DIR (USE DIR > DIR in DOS),
anyone can get a list of the files you have stored in it for
downloading by typing :QBM: DIR. Since they do not get the real
directory, just what was in it at the time you copied it into the
file "DIR", you may keep "hidden" files in this sub-directory.
You may thus leave a file for someone to download, tell them that
its there by leaving them a message (which they will get
automatically when they connect) and no one else connecting will
know that it is there.
If you want to upload a file, ":QDB:" allows you to upload text
or ASCII files.
If you use the "lan-linK" option of the Packet Terminal Menu,
LAN-LINK will automate the QDB and QBM features for you.
4.0 Path Determination to a DX station
If you want to establish a digipeat path to a station somewhat
out of your direct range, you need to know which of the stations
that you can connect to can hear that desired DX station. If you
could get a call monitored (MH list) from the stations that you
connect to, you would be able to see if the station you are
connected to has heard your desired DX station.
LAN-LINK uses the :QMH: command to request such a list. When LAN-
LINK receives a :QMH: command, it drops back to the TNC Command
Mode and issues a "MH" command to the TNC (except to a TNC1 which
does not support it). It stores the list received in a temporary
buffer, and then returns to the Converse Mode and transmits the
list back to the station it is linked to.
By judicious use of :QMH: you can determine paths to other
stations. Note however, that just because one station can hear
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 4 Page 131
another station, it does not mean that it can work it. For
example, the station you are connected to may be using a power
level of 1 watt or so, while the station 200 miles away that it
heard was using 100 watts. Test the path yourself, or/and leave a
message asking how reliable the connect path between those two
stations is.
If you and a small group use a non standard packet channel for
inter-group communications, you may also use the :QMH: function
to find out who the station you are connected with, has heard
recently, when you first sign on the LAN channel.
5.0 Binary File Transfers
In the PC world most binary file transfers seem to be taking
place using the YAPP protocol built into the YAPP user terminal
program and the BBS software written by Jeff Jacobsen, WA7MBL. As
Jeff stated in the documentation, YAPP was written to provide a
terminal program for use in testing the WA7MBL BBS code. However
for many radio amateurs, YAPP was their first terminal program.
The YAPP binary transfer protocol is similar to the Xmodem
protocol used on telephone line BBSs. In order to transmit a
file, the sending station breaks the file down into blocks of
characters. Each block is transmitted in sequence. After a block
has been transmitted, the sending station waits for the receiving
station to acknowledge that block and verify that it was received
without errors.
When two stations are alone on a frequency, they can transfer
data quite quickly. So back in 1986 when YAPP was written, it
provided the few hams using packet radio with a binary file
transfer capability. Today, however, the situation is different.
In most urban areas, each packet radio channel is occupied by
many stations, and the requirements for binary file transfers are
somewhat different.
6.0 Requirements for Transfer Protocols
The AX.25 protocol provides for a basic verification that packets
have been received error free. If the binary file transfer
protocol could establish the connection, start sending blocks,
and then keep sending data until one of three things happen; the
link drops out, the receiving station signals that some of the
data were received with errors, or the whole file is transmitted
correctly.
If the whole file is transmitted, then the sending station just
has to wait for an acknowledgment from the receiving station that
the file was received. If the circuit is busy with several
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 4 Page 132
stations on the channel, or the path goes through one or more
Nodes, there will be varying delays in the delivery time of the
packets. By not having to acknowledge each block of data, the
file can get through much faster than it would have, in the case
in which each received block has to be individually acknowledged.
If the link drops out, it would be nice if the computers, could
determine how much of the file was received, then pick up the
transmission at that point next time they link up.
If the receiving station signals that some data were received in
error, the sending station should then begin to retransmit from
the start of the error.
7.0 The Zmodem Protocol
This situation is not unique to the amateur radio packet network.
It is also present in the commercial packet switching
environment, and the Zmodem protocol was developed to provide the
capabilities described above. Zmodem thus seems to be an almost
ideal binary file transfer protocol for use on radio amateur
packet channels, and is incorporated in LAN-LINK 2.00+.
LAN-LINK uses the :QZD: and :QZU: commands to provide the
capability to remotely download and upload binary files. :QZD:
allows you to download a file from another station, while :QZU:
allows you to upload a binary file. :QZD: is configured so that
if the link drops outs during the transfer, when the connection
is once again established, a subsequent :QZD: for the same
filename, will cause the transfer to pick up where it left off
when the link dropped out. This feature is not allowed in the
upload :QZU: command to inhibit people from injuring files that
already exist on the other computer. Each command may be
initiated from either end of the link, but to gain the most from
the recovery capability, files should be downloaded by the
receiving station.
8.0 The PCZ Zmodem Package
LAN-LINK implements the Zmodem protocols using batch files in DOS
that call up external programs. This approach allows stations to
try different versions of Zmodem and experiment to find the
optimal one for their area. LAN-LINK comes with the (PCZ) Public
Domain implementation of the Zmodem, Ymodem, Xmodem, Xmodem-1K
and Sealink protocols by Drue Kennon and Gary Smith.
Since any LAN-LINK station can either receive or originate a
:QZD: and a :QZU: command, LAN-LINK comes with four default batch
files to control Zmodem transfers. These files are as follows.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 4 Page 133
QZU-RX.BAT Batch file implemented after receipt of :QZU:
QZU-TX.BAT Batch file implemented after transmission of :QZU:
QZD-RX.BAT Batch file implemented after receipt of :QZD:
QZD-TX.BAT Batch file implemented after transmission of :QZD:
Each pair of users can experiment with other protocols and Zmodem
implementations using the :QZD: and :QZU: commands after reading
the PCZ documentation. The :QBU: command can also be used if the
corresponding DOS batch files (QBU-RX.BAT and QBU-TX.BAT) are
created.
LAN-LINK contains an output buffer to store data being output to
the TNC. The TNC contains a buffer which stores data about to be
sent on the radio link. In the normal course of events, the two
buffers fill up, so that the Zmodem package used by LAN-LINK may
think that all the data has been transmitted, when in fact there
are still characters left in the buffers, or the last packet has
not yet made it to the destination station. In this case, you may
see a message on your screen that the system has sent all the
data and is waiting for the final acknowledgment, while at the
same time you can see from the LEDs on the TNC that you still
have outgoing data in your system. Have patience and wait a while
to let the two systems synchronize.
In the event that the link is bad and errors occur, this
buffering may cause problems which require some of the Zmodem
timing parameters to be changed. Should this situation arise,
read the Zmodem package documentation.
The flexibility offered by the Zmodem protocol has many
advantages when used in a packet radio network. LAN-LINK 2.00+
implements Zmodem by the use of an external public domain
protocol package which provides for the maximum degree of user
customization. This capability is provided at the cost of having
the individual user customize four batch files using the text
editor built into LAN-LINK.
9.0 BASIC NC/L DICTIONARY
Messages can be transferred into any other LAN-LINK computer you
can connect with using elements of the Q code adapted for the
purpose. NC/L command words are summarized in the following
paragraphs. There is no command word to request your message. To
receive your message, you do nothing. You will receive your mail
automatically when connecting/linking with a LAN-LINK station.
You cannot normally read messages addressed to another person.
9.1 :QBM:
To download an ASCII file, send ":QBM: FILENAME.TYP". The
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 4 Page 134
FILENAME.TYP is the file you want. i.e. ":QBM: DIR".
9.2 :QDB:
To upload ASCII files to another LAN-LINK system send ":QDB:
FILENAME.TYP". Files will be uploaded into the same sub-directory
as LAN-LINK, and will have a message header inserted at the top
of the file to allow the operator to know who uploaded the file.
If the operator then wants to make the file available for
downloading, he or she can move it to the \LAN- LINK\FILES sub-
directory. The ".TYP" following the filename is optional. If you
attempt to upload a file which has the same name as one that
already exists on the remote system, you will receive an "error"
message. This command is the reverse of :QBM:.
9.3 :QMH:
To request a call monitored list ("MH") from the LAN-LINK station
that you are connected with, send ":QMH:".
9.4 :QSM:
To request a repeat of a message from a station using LAN- LINK,
send ":QSM:". This command will be valid as long as the host
station has not deleted the YOURCALL.OLD file on his disk. If the
file does not exist, you will receive a :QNO: "error" response.
9.5 :QSP:
To leave a message, send ":QSP: callsign". The callsign is that
of the station you wish to leave a message for.
9.6 :QRA:
When disconnected, to see what stations (using LAN-LINK 1.53+)
are on the LAN, or which LAN-LINK stations have messages pending,
send ":QRA:". All LAN-LINK stations will reply with a mail beacon
within a few seconds. The Alt-W key implements this feature.
9.7 :QRT:
To shut down a LAN-LINK AMTOR/Packet mode Mailbox or beacon
station which is causing QRM, link or connect to the station and
send ":QRT:".
9.8 :QRU:
To upload messages from one LAN-LINK/PK232COM (1.38+) system to
your computer, send ":QRU:".
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 4 Page 135
You may only use the QRU function with stations designated as
Store and Forward mailboxes. Put a list of stations that you can
connect to reliably in your CALLSIGN.MBX file and send it to
other stations in your LAN also using LAN-LINK. They will then be
able to dump their mail messages on you and you on them. If they
do the same and send you their file, then you will be able to
send messages via them for stations that they can work.
While QRU gives you the capability to bulk upload messages to
another station in your local area, when you take your machine
off line, it may also be used to transfer messages between two
LANs via well sighted gateway digipeaters.
9.9 :QNO:
:QNO: and error message text is a response to a request.
9.10 :QJG:
:QJG: is a response to :QRU:. It confirms that the QRU sequence
is complete. There are no more messages pending.
9.11 :QRV:
:QRV: callsign is a response to :QSP: callsign. The computer is
ready to send the message. End the message with a control Z (^Z)
character, or the sequence :EOF:
9.12 :QSL:
:QSL: is a response to a command. It confirms receipt of message
to that callsign or that a file has been successfully uploaded
and stored to disk. It is also used to acknowledge receipt of a
":QRT:" command.
9.13 :QTA: message
If LAN-LINK receives :QTA: and a message exists for the
connecting station, LAN-LINK will change the filetype from "OUT"
to "OLD" and respond with a "QSL". If a message does not exist,
it will respond with a "QNO".
9.14 :QTC: Message List
If LAN-LINK receives :QTC: it will respond with the beacon text
showing the mail queue. :QTC: precedes a list of callsigns for
whom messages are stored up on a computer. It is used in Packet
Beacon transmissions or AMTOR Beacon mode CQ calls.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 4 Page 136
9.15 :QBU: External Protocols
This feature is supplied to allow experimentation with external
protocols.
9.16 :QZU: Zmodem Binary File Upload
:QZU: is used to implement an upload of a binary file from
another station using an external Zmodem protocol via the QZ*.BAT
files.
9.17 :QZD: Zmodem Binary File download
:QZD: is used to implement a remote download of a binary file
from another station using an external Zmodem protocol via the
QZ*.BAT files. In the event that the link drops out during the
transmission, when the link is remade, and the :QZD: retried, the
transfer will pick up from the point at which it was interrupted,
if the batch files provided are used.
9.18 :QIC: Page Operator
Use :QIC: to page the operator at any LAN-LINK 2.10+ station. The
sequence is:- you send :QIC: to another LAN-LINK 2.10 station.
Use the LAN-LINK Menu or type it by hand. Upon receipt, LAN-LINK
begins to page the operator if the sound flag is on. At that time
it sends you a :QRX: followed by a number, i.e. ':QRX: 30'. The
number is the number of seconds it will page the operator. At the
end of the paging sequence it will send the prompt i.e. 'G3ZCZ>'.
If the sound is inhibited it will send ':QRX: QRT' to signal that
it is in a silent configuration.
9.19 :QTR: Ask for Time
The :QTR: command allows you to get the date-time-text string
from the other LAN-LINK 2.10+ station. Don't confuse it with
:QRT:.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 5 Page 137
Appendix 5 Using Different TNCs
The Packet Mode capabilities can be used on all TNCs. There are
minor differences in the command dialogue between different TNCs.
The dialogue differences affecting the operation of LAN-LINK are
built into the program and set when the TNC type is read from the
LAN-LINK.SYS file at the program load time. The non packet modes
will obviously result in error messages if attempted on a packet
mode only TNC.
The following notes apply to different TNCs or digital
communications controllers.
1.0 TNC2 (MFJ 1270)
The following functions do not work because the TNC does not
support them.
All NON PACKET modes.
Software controlled HF/VHF switching.
Software controlled baudrate switching.
CQ/BEACON Packet terminal mode.
TNC Transmit Buffer flush.
N2GNJ noticed that he needed "LC ON" when using a Tiny 2 EPROM
Version 2.0 in the MFJ 1270B to make the automatic snatch
features work.
2.0 TNC1 (HK-4040)
The Packet Communications Mode header colors are not supported in
LAN-LINK for this TNC.
The following functions do not work because the TNC does not
support them.
All NON PACKET modes.
Day/Time functions.
MH and remote :QMH: functions.
MAIL Packet Terminal Mode.
CQ/BEACON Packet Terminal Mode.
TNC Transmit Buffer flush.
Conference and multiconnect modes.
3.0 Kantronics KPC-2
The Packet Communications Mode header colors are not supported in
LAN-LINK for this TNC.
The following functions do not work because the TNC does not
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 5 Page 138
support them.
All NON PACKET modes.
MAIL Packet Terminal Mode.
CQ/BEACON Packet Terminal Mode.
TNC Transmit Buffer flush.
4.0 Kantronics KAM
LAN-LINK switches colors when it sees the /V or /H following the
callsign in the packet header, or in the calls monitored ("MH")
list. If you are monitoring both HF and VHF simultaneously, the
colors will show you which radio you heard which signal on. If
the Mail-Snatch or the QTC-Snatch are triggered, LAN-LINK will
change modes and attempt the connect on the correct radio but
will not change the band/power information or the logbook to
reflect that change in the logbook or in the status window
display. Turn the DCD flag OFF for these automatic features to
work.
The following functions do not work because the TNC does not
support them.
TNC Transmit Buffer flush.
The SIGNAL Communications Mode.
The Alt-D key in the MORSE Communications Mode.
The AMSAT-OSCAR Menu does not allow UoSAT option, as the KAM does
not have 1200 baud ASCII capability.
5.0 PK-232
Turn BBS OFF, if you want the Alert Call, packet communications
mode header colors, and Digipeat Detect features to work,
otherwise turn BBS ON.
6.0 MFJ 1278
LAN-LINK assumes that the Radio 1 port is connected to the
VHF/UHF packet transceiver, and the Radio 2 port is connected to
the HF transceiver with the multi mode communications capability
(you may customize this however).
The MFJ1278 suffers from one major deficiency as far as LAN-LINK
is concerned. The Echo-As-Sent only works in the AMTOR
Communications Mode. That means that you will not see the
contents of a file echo in the incoming window as the file is
being transmitted in the RTTY mode.
The following functions do not work because either the TNC does
not support them or does not do so in a consistent manner.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 5 Page 139
Pactor
Type Ahead Buffer
TNC Transmit Buffer flush.
The SIGNAL Communications Mode.
The AMSAT-OSCAR Menu does not allow UoSAT option.
CW Identification.
7.0 Heath HK-21
K3WGF noticed that his Heath HK-21 TNC didn't seem to have the
proper circuitry to support true DCD on pin 8 of the RS232
connector. Even though the pin was labeled DCD it didn't signal
properly. Set the DCD function in LAN-LINK to OFF to make the
Capture-to-Disk close out normally rather than continue to remain
engaged.
8.0 PK-900 and DSP 2232
LAN-LINK supports dual windows, and some of the
communications modes. Otherwise, support is as if they were PK-
232s. Sometimes, LAN-LINK may take a few characters to
synchronize windows.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 6 Page 140
Appendix 6 Anomalies and Bugs
This section discusses various anomalies and bugs.
1.0 Command/Converse Mode Anomalies
Since the Program has no way to check the command/converse mode
status of the TNC, you may see various "Cmd:" and other "error
messages" from the TNC when using the menus or function key
commands. Ignore them for now. If you get an error message, try
using the function key again.
2.0 Buffer Messages in AMTOR Beacon CQ Mode
In the AMTOR Beacon CQ Mode, if the other station drops the link
while you are recording the text, BEFORE the callsign has been
recognized as a valid callsign, LAN-LINK will time out before
logging the QSO and restart the CQ sequence. If someone else
calls in before the time-out has occurred, the text from both
stations should be captured to disk, but the log entry may not
show both stations. You should compare the callsigns in the
logbook with the "RUN" file for QSO purposes.
LAN-LINK in the Beacon/Mailbox Mode, normally logs the contact at
the end of the line in which it recognized the callsign as a
valid callsign.
3.0 FEC +? Responses in AMTOR Beacon CQ Mode
In the AMTOR Beacon CQ or Mailbox mode, if another station sends
a +? in the FEC Mode, the beacon will attempt to send the LAN-
LINK.TXT file. The PK-232 however is not in the Converse Mode at
that time and will interpret the text of the file as commands. If
by some chance, the text corresponds to a valid command the PK-
232 will execute it and put the PK-232 in an unknown state and
you may not notice that it did. As such I recommend that the
first character of each line in the file LAN-LINK.TXT be a non
valid command character such as a number or a period (.) or
another punctuation sign.
4.0 Using a Monochrome Monitor
If you are using a monochrome monitor, the text you type into the
Outwindow may be fainter than the incoming text. This is because
of the default colors used. Change the colors using the Parameter
Menu.
5.0 The Packet Conference Mode
The Conference Mode has been tested on a PK-232, KAM, a SANYO
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 6 Page 141
MBC-675 which has a clock speed of 4.7MHz and other PC clones
with faster clock speeds. If you have problems with intermittent
selection of I/O channels try slowing down your CPU clock. There
is a software delay loop in the program that is used to allow the
TNC time to switch I/O streams after receipt of the stream change
command. This delay is there because LAN-LINK tests for a connect
on each channel before outputting any text, so that it does not
send un-addressed packets on non connected I/O channels.
6.0 Packet Conference Mode Disconnects
Any Packet conference Mode disconnect returns the TNC to the
Command Mode, even if you remain connected to other stations.
7.0 Strange Events
If the TNC does not use an interrupt driven serial port you may
experience problems when using baud rates greater than 1200. The
PK-232 DOES NOT LIKE LAN-LINK to use RS-232 baud rates faster
than 2400, and sometimes not even that. Use 1200 until YOU have
tested and ARE SURE that a faster one will work.
If you have any strange problems and are using an RS-232 terminal
baud rate between the PC and the TNC which is greater than 1200,
set the Terminal Baud Rate to 1200 and see if the problem goes
away.
Make sure that your configuration is set the way you think it is.
Verify it using the Parameter Menu.
You must have at least one common call or scan word in your SYS
file, or you will get errors when you update the SYS file.
8.0 *** DISCONNECTED
In the Packet Communications Mode, when you are connected to
someone and the TNC sends "*** DISCONNECTED" to the computer,
LAN-LINK thinks you have been disconnected and resets. This
normally only happens when a true disconnect occurs. However, if
the text shows up in the middle of a line being sent to you, it
will have the same effect. LAN-LINK will think that you have
disconnected if the DCD Flag is not set in the SYS file, and the
TNC does not use the DCD signal on pin 8 of the RS-232 interface.
9.0 *** CONNECTED
In the Packet Communications Mode, if you are monitoring traffic
on the LAN and someone sends a packet containing "*** CONNECTED",
LAN-LINK thinks you have been connected, if the DCD-Flag is not
set, and the TNC does not use the DCD signal on pin 8 of the RS-
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 6 Page 142
232 interface.
10.0 Greek Characters and Other Garbage in the Incoming Screen
If you see Greek characters in the Incoming screen you probably
have the wrong parity set in the TNC. First make sure that the
RS-232 baud rate is correct. If it is, take the batteries out of
it and reset it. If that fails, play with the parity. LAN-LINK
sets the serial port as configured in the TNC.SYS file for each
TNC. For example, for the PK-232 it is 8 bits, no parity. For the
TNC2, it is 7 bits. If you still can't get LAN-LINK to talk to
the TNC, set the interface to 7 bits in the configuration file.
11.0 Dumb TNC
If the TNC seems to respond to commands but is not sending
anything back, you may have one of two problems. You may have a
bad RS-232 cable with a wire disconnected. If the computer can
operate the TNC in another communications program, try to reset
the TNC, take the batteries out, etc. You may also have a not-so-
compatible PC.
12.0 Intermittent Lockup
Watch out for flow control problems on the cable between the TNC
and the PC and between the PC and the Display.
Versions of LAN-LINK up to and including 1.55 used software
handshaking. Anytime the program received a Control-S (^S)
character from the TNC it waited until it subsequently received a
Control-Q (^Q). These characters can appear on the LAN in a
binary packet, either when binary file transfers are in progress,
or in a Inter NET/ROM message. To avoid this lockup, a line
containing "MFILTER 19" was added in the LAN-LINK.SYS file for
the PK-232 to make the TNC filter the ^S character out and not
pass it to LAN-LINK. LAN-LINK 1.56 and onward use hardware hand-
shaking so this problem should not appear. However if the FLOW
and XFLOW parameters are not set to OFF in your TNC, LAN- LINK
can appear to lockup. Make sure that they are both set OFF in
your TNC.
13.0 Automatic Functions Don't Work
This usually happens with the KAM. Set the DCD Flag off, and the
automatic functions should work. Note that in this case the
multi-connect functions will not work.
14.0 BBS Zap Failure
If the BBS Zap hangs up in the middle of sending a message, the
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 6 Page 143
probability is that the LAN-LINK is waiting for the PBBS to send
it a word it recognizes. You have probably not configured the
"PBBS Read Subject" and "PBBS Message" Strings (lines 43 and 44)
in the LAN-LINK.SYS File (See Appendix 2, Section 18.18).
15.0 LAN-LINK Forgets the Band/Power Information
LAN-LINK picks up the band and power information from the
logbook. You can set them via the "0" option in the Parameters
Menu. If the logbook is empty, LAN-LINK will not remember the
settings when it is switched off. Put at least one entry in each
logbook.
16.0 Zmodem Binary Transfer Problems
Some stations perform binary transfers with no problems, others
seem to have problems. If you are having problems with the binary
file transfers make sure:
* You have enough memory left over after loading LAN-LINK to
run the external communications protocol.
* The QZ*.BAT files have the correct port and baud rate
values.
* The TNC is set for 8 bit transfers.
* Both stations are using the same data rate between the PC
and the TNC.
* The TNC does not filter any characters out of the data
stream, i.e. MFILTER or the equivalent parameter in your TNC
is not set.
* Make sure you try the binary transfers via the LAN-LINK
menu.
* Read the PCZ Documentation file and set the Environmental
variables correctly.
* If all else fails, try a different external protocol.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 7 Page 144
Appendix 7 Updates, Revision History
If you are updating from a previous version of LAN-LINK, the
following changes were made in recent versions of LAN-LINK.
2.00
ELMER, Alt-W, word wrap, G option in Edit menu, Strswitch chars &
error_st in sys file, added. KAM cw/cmd bug fixed, AMTOR sets
narrow shift, connect timeout configurable, KAM RX/TX inv added,
bell filtered out of connectee/log call, KAM cw and other
parameter changes, log power/band picked up from log, custom
word[20] in prompt, Elmer added, event timer 2/6 reset change, MH
fire delay for KAM, ^T filtered out in all tncs, #T in contest
text, NAVTEX and navy MARS enabled for KAM/MFJ1278, flag_XMITOK
added, base count added to SYS file, CTEXT saved.
2.10
PACTOR (KAM, PK-232) added. Converted to TP6, Bug fixes Init:
7/8bits, log package changed, Elmer.qso loaded at start-up, Elmer
RUN commmand, BBS custom commands, Flag_Inhibit_Logging, Logging
package, FLAG_Printer_Perm, TNC_parameter, mode at start up, QIC,
QMH in menu, QTR, LAN-LINK.OUT, ANSI Colors, PacketCluster Log
Search mode added. ELMER resets on disconnect, MFJ1278 radio port
customzable, Shut down flag 5 deleted, BBS upload states changed.
2.20
Converted to TP7. Scan word colors, PacketCluster DX Alert
colorized. 2.2 was really a bug fix version for 2.10 which should
never have been released and was replaced within a few days.
2.30
Support for PK-900 and DSP 2232. Better ANSI support. G-TOR in
KAM. Manual Mode, Z and B options added to BBS Menu. Expanded
PacketCluster support. Demo option added in LAN-LINK Menu. Radio
Menu added for Kenwood and Icom (untested). EDIT.EXE and
UPGRADE.EXE external programs added.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 8 Page 145
Appendix 8 ELMER An Expert System Based on a Finite State Machine
There are two versions of ELMER supplied with LAN-LINK. One is
built in for use in packet mode communications, when connected to
someone else. The second version is a stand alone version for use
in developing the text files and the logic. The stand alone
version lets you program and debug your own personal ELMER on
your own. The stand alone version is a separate product and
requires separate registration.
Most initial amateur radio contacts (QSO) are somewhat
repetitive, in that they send the same information each time. In
digital mode communications hams don't type exactly the same
information in every QSO, but in general the information
exchanged is a subset of a standard set. Hams have noticed this
phenomenon and have each created and used files containing
standard information. This fact was noticed years ago, and the
first so called "brag tapes" were invented to serve that need
back when they were using teletypewriters and generated paper
tapes for the standard information.
ELMER takes that concept a little further and provides expert
system. By parsing the incoming text, ELMER will recognize
certain words and transmit text files containing replies or
further questions, just as if the operator was at the keyboard.
Hams can use this feature to build a smart server they can put
on-line on the LAN. The server will prompt people and will serve
an educational purpose. ELMER can be set up to teach people about
packet radio, license upgrades, or anything else. ELMER can also
be programmed to recognize different languages and hold a
conversation in those languages. In fact, apart from the
dedicated educational and informational server applications,
ELMER may be configured with such a variety of vocabulary files
so as to pass the Turing test in most typical amateur radio
digital mode conversations.
1.0 INTRODUCTION
ELMER is a program which allows you to build an expert system. It
uses the ELMER.QSO file to set up the state machine.
The ELMER contains an array of words to be matched, current
states, next states, and files to be loaded.
The ELMER starts up in an initial state. When a line of text is
received, it begins to match an array of words against the
incoming line of text. It starts matching the words in the order
that they are present in the array. It only matches words that
are enabled for the current state or for state 0. If it finds a
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 8 Page 146
match, it advances the next state, and if a valid file name is
present (and exists), will output that file. The ELMER will then
continue scanning the line of text from the point that the last
match was obtained. At the end of the line, it waits for the next
line.
1.1 Expert Systems
Before discussing ELMER, here's some information about expert
systems. An expert system contains knowledge about a particular
field to assist human experts or provide information to people
who do not have access to an expert in the particular field. It
is an information system that can pose and answer questions
relating to information borrowed from human experts and stored in
the system's knowledge base. Although they vary in design, most
expert systems have a user interface, a knowledge base, and an
inference engine.
1.2 The User Interface
The User Interface to the expert system is the way that the user
interacts with the system to extract information from the system.
1.3 The Knowledge Base
The Knowledge Base of an expert system contains both declarative
and procedural knowledge. The facts describing the situations,
events and objects are called declarative knowledge. Procedural
knowledge is the information about courses of action and the
rules governing the actions. There are various kinds of rules
that may be employed.
1.4 The Inference Engine
The Inference Engine controls how and when the information in the
knowledge base is applied. It determines how the rules in the
knowledge base are to be applied to the problem.
1.5 Features of an Expert System
The following list of features are desirable in any expert
system.
1.5.1 Useful
The system should meet a specific need.
1.5.2 Usable
The system should function so that even a novice computer user
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 8 Page 147
finds it simple to use. It should be able to respond to simple
questions.
1.5.3 Educational
The system should allow non experts to increase their expertise.
In a similar vein, the system should be able to explain the
reasoning behind its advice to allow the user to determine the
validity of the advice.
1.5.4 Adaptable
The system should be able to learn new knowledge.
1.6 Using an Expert System
Expert systems take the form of software packages residing on a
hardware platform (computer). The most common use of an expert
system is via a man-machine dialogue. The user types something at
the keyboard and the system replies. The user interface accepts
the input. The input is parsed in some manner. The inference and
knowledge engines process the user input in a predetermined
manner and an output appears. The parsing function may be a
simple pattern matching method commonly called keyword analysis,
or a more complicated function using syntactic analysis. Keyword
analysis is a logical function in which the presence of various
keywords are detected. When a keyword is found, the system
responds in the manner in which it has been programmed. For
example, if the system detects the words "the wx" in a question,
it may respond with " the wx here is sunny".
In syntactic analysis, a sentence is analyzed according rules
which allow the system to respond differently to keywords which
appear in different sequences. For example, the system may
respond differently to the question "what is the wx" and "the wx"
if it recognizes those words in a sentence.
1.7 The Semantic Network
The most general and oldest artificial intelligence scheme for
representing knowledge is the semantic network. A semantic
network is a collection of objects called nodes. The nodes are
connected together by links. Ordinarily, both the links and the
nodes are labeled. A drawing of a semantic network contains
bubbles to represent the nodes, and lines connecting the nodes to
represent the links. Both nodes and links are labeled. The
drawing looks just like a PERT or CP/M chart. It is also the
drawing used to represent a state machine.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 8 Page 148
1.8 A State Machine
A state machine is a system that exists in several states. The
system makes a transition from one state to another as a result
of a stimulus. All states and transitions are defined at the time
the system is designed. The links in the semantic network are the
transitions in the state diagram.
1.9 The User Perception
The user perception of an expert system is that the system
appears to be in a rest state. It receives an input from the user
and enters a transition to a state in which it processes the data
it has just received. After processing the input, it generates an
output and returns to what seems to be the same rest state. In
reality, the two rest states (initial and final) are different.
1.10 ELMER
ELMER is an expert system for amateur radio. ELMER is based on a
finite state machine using table driven software. The declarative
knowledge is stored in the form of separate ASCII text and
command files. The procedural knowledge is stored in the state
table. The Data files in ELMER correspond to the Knowledge Engine
(and the Inference Engine). The State Tables correspond to the
Inference Engine. ELMER also contains an ASCII editor for text
files, and a tool to view the state table. These tools allow the
user to "teach" ELMER new knowledge.
1.11 Responses to an Input
ELMER has three kinds of reaction to a word match. It can do
nothing, output a test file, run a command or overlay a new state
table. ELMER's state table contains four entries:-
1.11.1 Current State
This is the state that the string match is performed in. ELMER
can have up to 63 different states.
1.11.2 Next State
This is the state that the ELMER will advance to if a string
match is found.
1.11.3 Repeat Flag
This is a flag to allow or disallow repeats. If it is a 0 repeats
are allowed. If it is a 1, they are not.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 8 Page 149
1.11.4 Command Flag
This is a flag to tell the ELMER how to treat the file. If it is
a 0, load a text file; a 2, overlay the current state table with
the defined one.
1.11.5 Keyword
This is the text string to match in the syntactic analysis of the
input text. The text string can be up to 15 characters long and
can include spaces. The match is case insensitive, i.e. there is
no difference between upper and lower case.
1.11.6 Data File
This is a text file to be loaded or a new configuration file.
1.12 Syntactic Analysis
ELMER performs syntactic analysis on the input text in the manner
described below. ELMER performs a string match on the line of
received text against each keyword entry in the state table.
ELMER starts with the first entry. If a match is made, ELMER
changes state and performs the transient function defined by the
Command Flag. All words in the input text including the keyword
are then deleted. ELMER then continues the string match until
either the input line of text has been reduced to zero length,
or, the line of input text has been tested against all keywords
in the state table.
1.13 Programming ELMER
Programming ELMER is simple. The knowledge base is broken out in
terms of states and transitions. States can be passive or active.
A passive state is one in which ELMER does nothing other than
accept/parse further input. An active state is one in which ELMER
loads and displays a text file containing information or shells
to DOS and runs an external program.
ELMER contains a set of tools for programming and debugging
purposes. A state table for the procedural knowledge is drawn up
using pencil and paper and a large sheet of graph paper. The
built in text editor is then used to enter information into the
table. The individual text files containing the knowledge are
also created using the editor. The state table viewing tool is
used to check the entries. The state table loading capability is
used to exercise ELMER and verify the logic. Because the
procedural knowledge is contained in the state table, all sorts
of rules and linkages may be used.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 8 Page 150
2.0 The State Table (ELMER.QSO) File
These are the contents of the ELMER.QSO file.
2.1 The Directory Path to the ELMER Text Files
This item is the directory path to the sub-directory containing
the ELMER text files. For example "c:\LAN-LINK\ELMER\" or
"c:\ELMER\" or just "c:", if you put them in the same sub-d-
irectory as ELMER.EXE. If you do use a path you MUST have the
last "\" character at the end of the sub-directory name because
the program concatenates the directory path to the ELMER.
2.2 The Start Up File
This line is not used in LAN-LINK's ELMER. It is only used in the
stand alone version. It contains the name of the text file to
output the first time ELMER is invoked (if present);
2.3 Window Colors
These seven lines are only used in the stand alone version. They
are the numbers which correspond to the colors of the seven
different windows displayed on the screen of the stand alone
version, in the following order.
2.3.1 Status Window Color
The color of the window at the top of the screen.
2.3.2 OutWindow Color
The color of the window in which the replies are displayed.
2.3.3 InWindow Color
The color of the window in which your keystrokes are displayed.
2.3.4 BottomWindow Color
The color of the bottom line of the screen.
2.3.5 Promptwindow Color
The color of the window in which menus are displayed.
2.3.6 Option Color
The color of the highlighted characters in the menus and prompts.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 8 Page 151
2.3.7 Alarmwindow Color
The color of the window in which error and alarm messages are
displayed.
2.4 The ELMER Initial State
This item is included to allow you to have different state
machines, each starting with a different state number.
2.5 State Machine Parameters
The next few lines contain the state machine parameters.
2.5.1 Current State
This is the state the string match is performed in. LAN-LINK
allows up to 63.
2.5.2 Next State
This is the state that the ELMER will advance to if a string
match is found.
2.5.3 Repeat Flag
This is a flag to allow or disallow repeats. "0" means that
repeats are allowed. "1" means they are not.
2.5.4 Command Flag
This is a flag to tell the ELMER how to treat the file as shown
below.
Flag Operation
0 Load/display a text file.
1 Execute a BAT, COM, or EXE file.
2 Overlay the current state table with the new one.
2.5.5 Keyword
This is the text string to match. It can be up to 15 characters
long and can include spaces. The match is case insensitive, i.e.
there is no difference between upper and lower case.
2.5.6 Data File
This is either a text file to be loaded or a command file to be
executed, depending on the state of the Command File Flag. An "*"
character defines a "do nothing" state in which the Data File is
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 8 Page 152
ignored.
The two character sequence "#1" will cause ELMER to clear the
screen before displaying the rest of the text in the data file.
2.6 The State Machine File
An example of some state machine parameters is shown in this
typical extract from an ELMER.QSO file.
1, 2,0,0,what,*
2, 3,0,0,englishman,*
3, 4,0,0,doing,*
4, 1,0,0,country,me-usa.txt
1, 1,1,0,equipment,pk232com.txt
1, 1,0,0,wx,localwx.txt
1, 5,0,0,kenwood,kenwood.txt
5, 1,0,0,811,811.txt
1, 1,0,0,hello,hello.txt
0, 1,0,0,name,joe.txt
An "*" character defines a "do nothing" state in which the Data
File is ignored.
2.7 Example of Programming the State Table
Consider a typical question that I get asked.
"what's an englishman like you doing in this country ?"
followed by
" The equipment here is ....."
Assuming that the ELMER is in State 1, and that the first few
lines in the ELMER.QSO file are as shown above. The ELMER
recognizes the word "what" and advances to State 2. Since the
file name is an "*" character no file is sent. The ELMER then
recognizes the word "englishman" and advances to state 3. The
ELMER machine then recognizes the word "doing" and advances to
State 4. The ELMER then recognizes the word "country" advances to
State 1 and transmits the text file "me-usa.txt", because the
Command Flag is a 0. It then recognizes the word "equipment",
remains in State 1 and transmits my brag tape file called
pk232com.txt. Since the Repeat Flag is a 1, the ELMER will not
retransmit pk232com.txt should it once again recognize the word
equipment while in State 1.
Since the ELMER scans sections of the line, the same effect will
be achieved if the incoming text had looked like :-
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 8 Page 153
"what's an englishman like you
doing in this country ?
The equipment here is ....."
You can only have 63 lines in any one state machine array. You
can define up to 64,000 different states. Each state must be an
integer. State 0 is a wild card state. This means that any word
in the array coded for state 0 will be matched against the
incoming text whichever state the machine is in. The entries in
the state machine file must end with a line that contains state
666. For example
666, end of file
The number of lines in the array and the current state at the end
of each line scanned are shown in the status window.
3.0 The Stand Alone Version Status Window
The Status Window provides you with some diagnostic information
about the state machine.
C: shows the current state.
T: shows the number of states (lines) in the state table.
ELMER.QSO represents the name of the current state machine.
4.0 The Stand Alone Menu
You bring up the menu by touching the "Escape" character. You are
then presented with the options shown in Figure 8-4. To activate
an option touch the highlighted key.
Figure 8-4 ELMER Menu
E Edit Any File
L Load ELMER.QSO
P Pick File to edit
S Edit ELMER.QSO
X eXit to DOS
* Show State Table
4.1 Edit Any File
This option allows you to edit text files using the LAN-LINK
compatible text editor.
4.2 Load State Table (ELMER.QSO)
This option allows you to reload the state table, or load a
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 8 Page 154
different one. If a different state table is loaded, its name
will appear in the menu.
4.3 Pick File to Edit
This option allows you to pick a file with the default filetype
of "TXT", and edit it.
4.4 Edit State Table (ELMER.QSO)
This option allows you to edit the state table (configuration)
file.
4.5 eXit to DOS
This option allows you to exit to DOS.
4.6 Show State Table
This option allows you to see the contents of the state machine.
It is used in debugging the logic to ensure that the contents of
the table match what you thought you put in.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 155
Appendix 9 PCZ Binary file Transfers
LAN-LINK uses the PCZ public domain external protocol for binary
file transfers by shelling to DOS and executing the QZ*.BAT batch
files. The QZ*.BAT files are set up for you by the INSTALL
program. This appendix contains the documentation for PCZ as
supplied by the developers of PCZ, in case you have problems
making binary file transfers work in your system.
PCZ - A Public Domain implementation
Zmodem, Ymodem, Xmodem, Xmodem-1K, Sealink
for the IBM PC family
PcConnect Zmodem by Drue Kennon and Gary Smith
PCZ is a public domain Zmodem implementation that will allow
users of communication software that does not implement internal
Zmodem to access it through an external program. It is a full-
featured version of Zmodem, but does not have the large volume of
bells, whistles & options provided by Omen Tech's DSZ. However, I
do believe that it will be suitable for the average demanding
BBS'r.
PCZ provides support for the basic Xmodem variants: Xmodem,
Xmodem-1K, Ymodem & SEAlink.
The following is a description of how to start PCZ for file
transfers.
LEGEND
Data enclosed in "[" "]" are optional.
Data enclosed in "<" ">" are required.
Send Command line:
PCZ <1-8> <300-19200> [m] [f] [d] [s] <s?> [r] [@]<filespec>
Recv Command line:
PCZ <[1-8]> <[300-19200]> [m] [f] [k] [d] [s] <r?> [r]
[filespec]
Ref:
1-8 - the number 1 - 4, -(8) << PS/2 >>
300-19200 - the number 300, 1200, 2400 etc...
m - front-end menu option (see MENU)
f - enable FOSSIL comm driver routines
k - rx keep aborted received files
d - disable video memory writes (use dos)
s - request enable Super_Z transfer mode (zmodem only)
r?,s? - transfer type sz, rz, sx, rx etc...
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 156
r - resume/recover aborted transfer (zmodem only)
@ - command file transfer alert flag (SEAlink, Z,Ymodem)
filespec - file name w/extension {complete file spec
allowed} {drive:\path\filename.ext}
Flags should be placed as shown for standardization purposes.
i.e. "f" before "d"; "d" before "k"; "rz,sz" before "r" etc...
Due to the nature of the beast, no support is provided for a
default port & no default port speed is assumed.
NOTE * See environment variables below for more on default
port/speed
I personally never enter "port" or "speed", but always enter
their values. i.e. pcz 1 9600 f sz xxxxxxx.xxx The batch files
included reflect this method.
"ZMODEM RECEIVE"
<< SINGLE >>
PCZ 1 9600 rz myfile.ext - assume your specified file name.
<< BATCH >>
PCZ 1 2400 rz - Receive ALL sender files.
PCZ f d k rz r - Receive ALL sender files
assume PCZPORT & PCZSPEED values
use FOSSIL routines
use standard DOS screen output
KEEP all aborted files.
RESUME any incomplete previous files.
one file mode:
PCZ 1 9600 rz INFILE.ARC - Receives one file and names it
INFILE.ARC
PCZ 1 9600 rz r INFILE.ARC - Recovery effort on file
INFILE.ARC
NOTE * A word about command line switches might be in order here.
The switch flags " f, d, k " are global. That is they control PCZ
and not any particular protocol. The "r & s" switch is isolated
within zmodem, but is applied to both sender and receiver. If you
want PCZ's resume code enabled when sending a file then the
sender must specify "r" on the command line. Accordingly if the
receiver requests resumption of an aborted transfer, the sender
must have "r" specified or we won't resume anything. This was
requested by BBS Sysops who track download bytes, transfer points
etc... Probably so you aren't charged twice or the such like.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 157
"ZMODEM SEND"
<< SINGLE >>
PCZ 1 9600 sz OUTFILE.ARC - Send one file to receiver.
<< BATCH >>
Create a TEXT command file with one complete file spec per line,
which includes drive and directory information for each file that
is not in the directory PCZ was called from.
e.g. C:\MYDIR\THISFILE.ZIP
There is NO limit to the number is allowed. Have no blank lines
in the file. Place the "@" symbol as the first character of the
filename.
Pass it to PCZ on the command line as follows:
PCZ 1 2400 sz @OUTFILE.TXT
What you name the command file is your business. It simply must
be a standard ASCII file with no software or printer control
codes present.
An alternative to creating the command file for sending 2 or 3
files may be used. Simply type the file names on the dos command
line separating each one with a space.
Remember the receiver must be set to accept batch uploads or you
might be spinning your wheels. Some BBS packages are just now
coming on-line with batch upload features using PCZ. They
normally indicate (BATCH) if it is supported.
BBS << BATCH >>
One method for implementing batch uploads on a bbs is to use the
log file and examine the transfer status character. The first
character of each line in the log file denotes how the transfer
finished. A "1" for good transfer & "0" for a failed transfer.
Armed with this information, simply setup to call PCZ in batch
receive mode. After PCZ has finished and your bbs code has
control, open the logfile and read in the line(s) of information.
You may now format a string to send the user about the status of
each file he/she sent, prompt for a file description etc..
After you have dealt with each entry in the logfile, simply close
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 158
the file and delete it. PCZ will create a new file for the next
transfer session. If you desire a continuous record of the
transfers then you should create your own and append each entry
you read from the pczlog to your continuous log file.
The information below shows exact start positions for each piece
of data. The x's denote the length of each element, the first (x)
shows start position as PCZ will write it to the log.
e.g. Below, the file size is 47877. PCZ will always write the
file size as a 7 character string which begins at position 21 in
the line. Hence, read from pos (21) to pos (27), trim any blanks
& convert to decimal value etc..
Log extract w/char positions:
1 2 3 4 5
1234567890123456789012345678901234567890123456789012345
x xx xxxxxxxxxxxx xxxxxxx xxxxxx xxxx x
1 sz PCZ40x.ZIP 47877 @ 2400 bps @ 237 cps 0
6 7 8
6789012345678901234567890
xxxxxxxxxxxxx
errors Fri 10/5/1990
"XMODEM VARIANTS"
To receive files using any of the Xmodem variants, the format is:
PCZ <port> <speed> rs filename - SEAlink receive
PCZ <port> <speed> rs - SEAlink Batch receive
PCZ <port> <speed> rx filename - Xmodem receive
PCZ <port> <speed> r1 filename - Xmodem-1K receive
PCZ <port> <speed> ry filename - Ymodem receive
PCZ <port> <speed> ry - Ymodem Batch receive
Remember the "k" option works for all of the receive modes. Hence
you can receive a file via SEAlink, have it abort on errors, and
then later RESUME the transfer using Zmodem.
To send files using any of the Xmodem variants, the format is:
PCZ <port> <speed> sx filename - Xmodem
PCZ <port> <speed> s1 filename - Xmodem-1K
PCZ <port> <speed> sy filename - Ymodem *
PCZ <port> <speed> ss filename - SEAlink *
* Refer to Zmodem Batch sending for batch transfers via Ymodem
and SEAlink
NOTE: The bytes and cps rate reflect the actual number of bytes
sent to, or received from the IOBuffer as a transfer progresses.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 159
It does not necessarily reflect any specific "BLOCKSIZE". When
sending, as a transfer nears it's end, you will see the cps
decline. That's because PCZ uses buffered output vs a simple
"sector size" buffer. This will let you see actually how PCZ is
progressing in the transmission of data. In the best case "Full
Streaming Zmodem", you will see the time for actual file data;
worse case time will reflect the transmission of data headers and
block acks. It is different, but I hope everyone can appreciate a
more accurate account of what is happening inside the powerful
zmodem protocol.
** : The "Transfer Time" reflects PORT speed, (NOT MODEM) speed!
If speed conversion is being used, FORGET the transfer time.
"ENVIRONMENT VARIABLES"
PCZ supports several environment variables which can make setting
up a comm pkg. or BBS more "user friendly". These variables are
as follows and should be placed in the autoexec.bat file as I
have them shown here or modify the setenv.bat file included to
accommodate your system.
"DRIVE" refers to the letters "A".."Z"
"YOURDIR" refers to a complete directory specification.
i.e. \COMM\ARC\
"YOUR.FIL" refers to a filename with extension that you want PCZ
to use vs it's default name.
"DIRRX"
set DIRRX=drive:\yourdir\
This variable provides the ability for all your received files to
be placed in a single location. It is very useful for bbs
purposes as well as general comm program usage. If you specify a
directory spec on the command line, it will override DIRRX.
Therefore you can easily set the variable and then just forget
about it. If DIRRX isn't set and no spec. is given on the command
line, your receive file will be created in the current active dos
directory.
"PCZLOG"
set PCZLOG=DRIVE:\YOURDIR\
In the log file's case, it specifies the directory you want your
PCZ.LOG file to be kept in. If "PCZLOG" is not found in the
environment then no log file is generated.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 160
set PCZLOG=DRIVE:\YOURDIR\YOUR.FIL
As an option to the log file name "PCZ.LOG" you may specify your
own filename in the filespec. This provides greater flexibility
with some bbs packages such as RBBS which expects it's own naming
convention to be used, and for multitasking environments etc...
If your "YOUR.FIL" exist, it overrides filename "PCZ.LOG" in all
cases.
"PCZPORT"
set PCZPORT=(1-8)
PCZ will use the port number (1-8) as the default port.
"PCZSPEED"
set PCZSPEED=(300-19200)
PCZ will use the speed (300-19200) as the default speed.
NOTE ** If you specify the PORT or SPEED on the command line, it
will override a default set by the environment variables.
"PCZDIR"
set PCZDIR=DRIVE:\YOURDIR\
If you experience any problems with PCZ not being able to access
it's overlay file, setting this variable will cure the problem.
DRIVE:\YOURDIR\ should point to the directory where you have
located PCZ.EXE
IMPORTANT NOTE:
NO SPACES are allowed when setting an environment variable!
i.e. {WRONG}
set PCZLOG = C:\COMM\ will not work.
That's not my fault. It is just DOS....
i.e. {ahhhh}
set PCZLOG=C:\COMM\
"PORT & IRQ"
It has seemingly become necessary, instead of interrupt sharing,
to reassign Comm. PORT addresses and use seldom triggered IRQ
lines e.g. "5 & 7" to allow multiple "more than two" ports on one
machine. Efforts to support this trend have been successful with
PCZ. Referring back to our PCZPORT environment variable:
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 161
set PCZPORT=1
If you have reassigned your IO card addresses etc..., you can
force PCZ to comply with your wishes.
Lets say you want to use PORT 3 @ 2E8h on irq 5. You set PCZPORT
in this manner.
set PCZPORT=3,2E8,5
| | |
| | |____ IRQ line number
| |_______ PORT address
|__________ PORT number
If you specify an invalid address or one your card isn't set for,
then PCZ will simply abort during it's port validation routine.
This method should provide the support needed for those who like
to match their wits against the cpu's.
"Super_Z" (tm)
Always in search for faster from fast. Super_Z takes zmodem to
the ragged edge! If you are one of the blessed, and enjoy
relatively noise free transmission lines, you should see an
increase of 2 to 3 % efficiency. XON/XOFF MUST be disabled and
the modem must pass these characters. You may activate Super_Z
via the command line switch "s". As is usually the case, Super_Z
can be called by the receiver or by the sender. That is to say,
that either can flag for Super_Z and if the remote version
supports Super_Z, we're doing it.
Regarding noise, a seldom thought of fact is that just because
your local transmission lines are great to one place, someone
else's local lines may be the pits. A good example is.... When I
log on to the "Corner" from Texas on a "596" extension I rarely
ever get a line hit. When I use the "995" extensions I am prone
to hits anytime. A reverse situation might occur in your
particular area. It simply depends on the quality of any of the
many exchanges you might encounter. I can only hope you are one
of the lucky ones.
"NETWORK SUPPORT"
PCZ has been tested completely in a network environment. It will
allow multiple users to read the same file via use of DOS's
shareable attribute. It will also lock any files that it is
currently writing to. This has been tested using Novell Netware,
LAN Manager, and CBIS Network-OS.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 162
"MENU FRONTEND"
Many fine programs exist which allow protocol engines to be
called from a communications package. In an effort to make PCZ
all the more user friendly, there is now a simple menu system
built into the program. It is controlled by the file PCZ.CFG
which is included in this zip file. Take a few moments to read
over it. It may be that it is just what you are looking for in
the way of a nice user interface. The design and layout of the
system is very simple and straight forward. You control the
options and protocols you wish to have active. PCZ.CFG comments
explain the various functions you can use. To use the menu system
simply call PCZ in the following manner.
PCZ m
Make your menu selections and complete the command line with your
filespecs.
"FOSSIL SUPPORT"
FOSSIL is an acronym for "Fido/Opus/SEAdog Standard Interface
Layer". This version of PCZ implements the use of FOSSIL
communications support. To date only one, "X00.SYS" driver has
been tested to work with PCZ. X00.SYS is a product of Raymond
Gwinn. It has proven itself in many environments and I recommend
it to you without reservation. X00.SYS was chosen because it
provides "FIFO" etc... support for the 16550 UART chip. My
internal routines support the chip but not all it's features.
Also X00.SYS provides enhanced ability to work in a multitasking
environment such as DeskView. If DeskView is active PCZ gives
idle processor time back to the cpu for smoother operations. For
a brief description of setting up X00.SYS on your system read the
enclosed file PCZFOSSL.DOC
Making use of the driver with PCZ is as simple as adding "f" to
the command line. It should be placed after the baudrate in all
transfer types.
i.e. PCZ 1 9600 f sz OUTFILE.ZIP
When PCZ starts, it will check for the presence of the driver in
memory. If it is resident all will proceed as planned. If
however, the driver is not in memory, PCZ will gracefully shut
down with a message stating this fact. I gave careful thought to
jumping to the internal routines, but decided against it for a
couple of reasons. In some cases the ports may be scrambled which
will surely cause a system lockup on PCZ's part. A problem may
exist with the driver you are using, giving false info which
PCZ's routines would not like very much. A "dumb" terminal might
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 163
have charge of things and not want another routine hanging
around, etc...
"PHONE SUPPORT"
Phone support can be provided when you require it, if you call
while I am home. I umpire for our local women's softball league
on Mon. & Tues. nights. I play golf on Wed. & Thurs. evenings.
Fri. night I do what Maureen tells me to do! Sat. is up for grabs
and Sun. morn & evenings I am in church. Please try me sometime
other than those mentioned ...... Seriously though, any night
(late) will be fine. Just try and make it before 10p.m. CST if
possible.
Note from the author:
Over the last year PCZ has received some very good reviews. More
users rely on the program for their transfers now than I thought
would ever be interested. For this I am especially grateful and
would thank each one if possible. Gary & I will continue to grow
with the needs of the BBS community. We ask for your continued
input and support, with our assurance that your IDEAS, "cheers &
jeers" are taken with sincerity.
Thanks
Drue
History
-------
V1.01.88 - Initial release, no known bugs. Please report any
problems to Drue Kennon.
V2.01.89 - Extended version that contains Xmodem, Xmodem-1K,
Sealink, and Ymodem Batch in addition to Zmodem. Also provides
full file sharing for use in networking environments.
V2.11.89 - Fixed several reported bugs. Enabled hardware flow
control for use with MNP type modems. Enhanced port speeds up to
19.2k, and tightened some code for more efficient operation.
Properly set errorlevel 1 in event of transfer failure.
V3.03.90 - Fixed a problem with SEAlink xfers not seeing the
last EOT. Batch sending for SEAlink per request. Enhanced some
screen data writes.
V3.06.90 - Fixed a problem with SEAlink xfers created by making
the last fix. Zmodem command file name can't be fouled due to
misunderstanding the docs.
NOTE:
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 164
Unless forced into it by the users, I do not plan to support 7
bit data transfers. Nor can I figure why any IBM machined BBS
would? Did I miss something along the way?
V3.08.90 - Got with the program and added support for FOSSIL
driver. e.g. Gwinn's Communications Controller, X00.SYS add "f"
to cmd line params for fossil). Removed internal support for
default port and speed which caused problems for multitaskers.
Defaults are now specified through environment variables. Added
environment variable for default receive dir. Reinstated environ-
ment variable for pcz log file.
V3.09.90 - By popular demand, namely "Gary", I added yet another
multitasker enhancement. Since the cpu is much faster than the
port, idle time occurs during output. This time is now "given
back" to the cpu, allowing the "other side" to operate smoother
and more efficiently.
V3.10.90 - Some users mentioned that PCZ would wait forever in a
transfer if the carrier was lost. I couldn't dupe the problem,
but added several more checks nonetheless. The logfile has
changed so that you may specify a full filespec. including
filename for you logfile in the env. var. The first char of each
line in the file represents pass or fail. "0" = failed xfer "1" =
good xfer. Keep those cards and letters coming!
V3.11.90 - ArrrrG! %#^^#%%@#*$(%*#$%($$%&*( the &*&^*&^ woes of
changes really &#$^& my &(&^#$.
V3.12.90 - Forget 3.11.90 ever existed! Several routines got a
face lift! You should see more efficiency with this release. I
can't begin to go through the entire chase with you here, but I
need a new can of RAID! Seems there is never a total end with a
bug problem, in programming as well as the home! I must offer a
special word of thanks to Dick Melville from San Marino for his
the help with RBBS interface problems. Dick was an excellent BETA
Buster! And to Steve Clancy who finally helped me see there was
NO carrier on the line!
V4.00.90 - {BETA} Version 4.00 represents a major revision
change to PCZ. As you have noticed, if you've used prior
versions, there are two PCZ files now instead of one. PCZ.EXE is
the global executable file and PCZ.OVR contains the actual
protocol functions. The decision to go with overlay functions was
made due to the fact that more Sysops are using PCZ with their
BBS's in a multitasking environment. Memory usage has been
drastically reduced. Additionally, each transfer type function
i.e. "sz,sx(1),ss,sy" & "rz,rx(1),rs,ry" is totally self
contained which simply means once the program loads and a
transfer type is called, no other overlay read is needed. The
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 165
function completes and exits. Simply put; execution time has been
enhanced.
V4.01.90 - {BETA} Dick & Steve
V4.02.90 - {BETA} Dick & Steve
V4.03.90 - {BETA} PcConnect, Dick & Steve
V4.04.90 - {BETA} PcConnect
V4.05.90 - Major revision V4.xx.90 released on the world!
V4.06.90 - Some enhancements added here include; Super_Z (tm) by
PC² , offers enhanced transfer times when used with error
correcting modems and relatively noise free transmission lines.
No limit to the number of files allowed in a batch transfer
command file. Non-standard PORT, IRQ line assignments supported
via environment setup. Frontend menu system for comm package use.
PCZ is supplied as a ".EXE" file which when executed breaks it's
code out into overlays. The largest executable code segment will
run well inside of a 64k memory segment.
Personal contact may be made by one of the following methods.
Drue Kennon Gary J. Smith
Rural Route #2 Box 54 6122 Cedar Wood Drive
Center, TX. 75935 Columbia, MD 21044
Voice 409-598-3809
The Programmer's Corner
Home of
"PcConnect" & "PCZ"
Data/BBS: 301-596-1180 Data/BBS: 301-995-3744
Data/BBS: 301-621-4636
10 roll over lines in place
with over 1.5 gigabytes of
storage space
DSZ, ZCOMM, Professional-YAM are Copyrights of Omen Technology
Inc, all rights reserved.
X00.SYS Copyright (c) by Raymond L. Gwinn, All Rights Reserved.
PCZ Copyright (c) by Drue Kennon, All Rights Reserved.
Super_Z(tm) is a trademark of PC²
** If you are the author of a communications package that has
zmodem implemented internally and would like to enable Super_Z in
you program for PCZ compatibility, look over SuperZ.Doc. If you
have any questions or problems then just drop me a line or call
and we will be glad to help you out.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 166
The PCZ Menu Transfer System
This is the PCZ.CFG file.
;To make use of this transfer menu system PCZ should be called in
the following manner.
;PCZ m <ENTER>
;We assume in this config file that you are using SETENV.BAT to
preset your PCZ parameters for PORT and SPEED. If this isn't the
case then simply add them on the protocol lines below in their
proper place. You should be able to see from the listings the
format used here. i.e.
;SEND without the ";" begins send protocol block
;END without the ";" end the protocol block
;The protocol goes on a line followed by the ":" char followed by
PCZ's command line options for that protocol. You will be
prompted to complete the command line with your filespec(s) once
the program is started etc... pretty simple huh?
;Simple yes! but simple minded as well, and if you fail to follow
these guidelines.... who knows what type of protocol you might be
trying to use for a transfer. Just to satisfy your cats curiosity
you may uncomment the first line after SEND. Run PCZ using "m"
menu option, select upload and see what happens. No your pc won't
bark but it might barf if you select "A" as your protocol type.
;The following represent the send parameters. Using the ";" at
the beginning on a line comment out any protocol you do not wish
to use during you file transfer sessions.
SEND
;flag for beginning of send protocols
;TOSSIT: sp ;This is a curiosity test line
;XMODEM: sx
;send a file using xmodem
;X1K: s1
;send a file using xmodem 1k blocks
;YMODEM: sy
;send a file using ymodem with file header information
ZMODEM: s sz
;send a file using Super_Z zmodem
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
APPENDIX 9 PCZ 4.06.90 Nov. 27, 1990 Page 167
SEALINK: ss
;send a file using sealink
END
;end of send protocols
:The following represent the receive parameters.
RECEIVE
;flag for beginning of receive protocols
;XMODEM: rx
;recv a file using xmodem
;X1K: r1
;recv a file using xmodem 1k blocks
;YMODEM: ry
;recv a file using ymodem with file header information
ZMODEM: s rz
;recv a file using Super_Z zmodem
SEALINK: rs
;recv a file using sealink
END
;end of receive protocols
;You may add any of the other command line switches you wish to
the above. They are
; "f" use FOSSIL
; "d" no direct screen writes
; "k" keep all aborted downloads
;Thanks and have fun!
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 10 Other Products by Joe Kasser, W3/G3ZCZ, Page 168
Appendix 10 Other Products by Joe Kasser, W3/G3ZCZ
1.0 PC-HAM 3.52
PC-Ham contains the following suite of programs.
1.1 LOGBOOK
Full blown logging package. With automatic check of logs for
awards such as DXCC. Allows you to recall any entry by call sign
within seconds. Indexed displays, QSLing, Contest mode QSLing
(prints the lot) and lots more. Although written in dBASE3 the
package contains a compiled version (LOGBOOK.EXE), so you don't
need dBASE to run it. The source code is ONLY given to registered
users. It can convert your exported LAN-LINK.LOG file to LAN-
LINK.DBF to put this package to work. Ideal for DX-peditions or
for DX robot users to handle QSLing and log statistics.
1.2 CONTEST
Keeps Dupes in memory, logs QSO's to disk in format which can be
processed by the LOGBOOK package. Now compiled in Turbo BASIC,
source code is supplied so that you can modify the program to
meet your requirements.
1.3 CQSS
Sweepstakes game compiled in Turbo BASIC. Work the ARRL
Sweepstakes contest on your computer. You are located just
outside Washington DC. A propagation model is built in to the
program. This program is REQUIRED training for all sweepstakes
operators. Earlier version of the program is described in detail
in Software for Amateur Radio by Joe Kasser G3ZCZ, published by
TAB Books, Blue Ridge Summit, PA. 17214.
1.4 WHATSON
Predict HF Propagation for given days. Contest mode with printout
to whole world at hourly intervals. Needs BASIC.
2.0 STARTREK The Computer Program
An ideal task for the beginner to learn a language on, is a
simulation game which is written to run on a computer that the
beginner has access to. For in that case, there is complete
control of all inputs and outputs. This kind of game (in which
the player makes decisions based on the information available to
him or her available at the time), can be made sufficiently
sophisticated and complex so as to make writing it an adequate
challenge for anybody.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 10 Other Products by Joe Kasser, W3/G3ZCZ, Page 169
The techniques used in writing a good game are the same that
programmers use in professional activities. Writing a good game
poses a challenge that allows you to develop good habits and
techniques for programming and also allows you to learn a
language in an interesting manner. By taking an orderly approach
to the game design, complex operations may be clearly understood
and converted to computer code with the aid of a language
reference manual, irrespective of the language being used.
This product teaches the techniques for writing such a game using
the STARTREK game as an example, and the BASIC language as the
programming language in which to write the code.
Registration fees.
Single Copy $15.00
10 - 50 Copies $12.00 per registered copy.
50 - 100 Copies $10.00 per registered copy.
100 + Copies $8.00 per registered copy.
3.0 WHATS-UP 1.30
WHATS-UP is a tool for experimenting with orbital dynamics and
Telemetry Decoding and display Program for the UoSAT-OSCAR 2,
AMSAT-OSCAR 13, Fuji-OSCAR 20 and the AMSAT Microsat Spacecraft
(OSCARs 16, 17, 18 and 19). It is table driven via the
configuration files to allow maximum flexibility.
WHATS-UP contains the following features:
Can beacon [APRS] and/or automatically attempt a connect to
MIR/SAREX: Can automatically set Kenwood Radios to spacecraft
beacon frequency when satellite comes over your horizon: Can
automatically read the frequency from Kenwood Radios to a disk
file for Doppler frequency measurements: Can automatically
configure a PK-232 for each spacecraft data format: Reads 2 Line
and AMSAT format orbit element data files: Provides antenna
azimuth and elevation pointing data: Real time, Playback and Dumb
Terminal mode: Automatic logging of AOS in LAN-LINK compatible
logs for AOS time analysis: Automatic Capture-to-disk of raw
telemetry. Extracts telemetry channel data to a database or
spreadsheet readable file for further analysis: Link quality
measurement on packet telemetry:
Capability to print the raw telemetry as it is received: Up to 16
user configurable display pages (screens): You set the position
on the page (width of engineering unit field, and number of
decimal places) that a parameter is displayed at: Wild card page
(parameter shows up on all pages): Selectable display of
Engineering units or raw byte for each display page: Display of
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 10 Other Products by Joe Kasser, W3/G3ZCZ, Page 170
raw packets (i.e. STATUS) Color changes if a parameter value
changed between successive frames: Audio and visual alarms if a
telemetry value exceeds, falls below or falls outside a preset
limit value(s): Dumb split screen terminal mode (in the manner of
LAN-LINK): Customizable colors, PC to TNC baud rate, data parity
and stop bits: Default spacecraft configuration files: Time of
day clock display (in HH:MM:SS format). Real time analysis
requires a receiver and demodulator. Analysis of playback data
can be performed with just the computer and WHATS-UP.
If you would like a copy of WHATS-UP and have captured any
telemetry to disk, especially daytime or southern hemisphere
passes, please put them on a disk and send it in with your
request, a mailer and return postage. Don't let the individual
data files become too long. I suggest that you rename them every
day in the format YYMMDD.SC, such as 900824.D17, 900824.F20, etc.
IF YOU ARE INTERESTED IN OSCAR AND SPACECRAFT TELEMETRY, THEN
THIS PROGRAM IS A MUST.
4.0 ELMER 1.00
ELMER is an Expert System Based on a Finite State Machine. There
are two versions of ELMER supplied with LAN-LINK. One is built in
for use in packet mode communications, when connected to someone
else. The second version is a stand alone version for use in
developing the text files and the logic. The stand alone version
lets you program and debug your own personal ELMER by yourself.
The stand alone version is a separate product and requires
separate registration.
5.0 BASIC PACKET RADIO
Basic Packet Radio explains how the computer can be used to
smarten up your use of packet. Not only does the book explain
packet radio, it comes with a full feature version of LAN-LINK
(for the PC) on disk and contains the manual for the program.
The topics covered in the book are outlined below.
Getting Started in Packet Radio, What Packet Radio Is, The Shared
Radio Channel, The Virtual Channel, The Equipment Needed to Hold
a Packet QSO, The TNC, TNC Modes, The Terminal Program.
Connecting the PC to the TNC, Command Convention, Making the PC
Communicate with the TNC, Determining and Changing the State of a
Parameter, Setting the Carriage Returns and Line Feed Display
Controls, Flow Control, Connecting the TNC to the Radio, Delays
in the Transceiver.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 10 Other Products by Joe Kasser, W3/G3ZCZ, Page 171
The Local Area Network, How TNCs Communicate, Controlling the
Display of Monitored Packets, Setting Your TNC to Display or
Ignore Packets, The Wireless LAN, Use of Packet Beacons, The
Alert Call, The Target Call, LAN Answering Machine, Mail Beacon
(Annunciator), Remote Beacon Shutdown.
Connecting to Someone, Connecting to Other Stations the LAN-LINK
Way, The Point and Shoot (MH List) Way, Using the Call Menu, Loop
Backs, Names, Handles and Paths, Connecting via NET/ROM and
TheNet, Connecting via KA-Nodes, The SAREX Call and Working MIR.
Extending the Range, Digipeating, Using NET/ROM and TheNet Nodes,
Using G8BPQ Nodes, Using KA-Nodes, Using MSYS Nodes, Using ROSE
Switches, Using LAN-LINK to Communicate via Nodes, Path
Determination to a DX Station, Finding Packet Signals, Using
Communication Satellites.
The Packet Bulletin Board System, How to Connect to the PBBS,
Connected to the PBBS, Connected, But What Next ?, Telling it
Your Name, Getting Information about the PBBS Itself, The Command
Prompt Line, Changing the Prompt Line, Listing the Messages and
Bulletins, Reading Messages, Sending Messages, Sending Messages
Around the World, Sending a Bulletin, Forwarding Bulletins,
Sending NTS Traffic, The Parts of the NTS Message, Killing
Messages, Using LAN-LINK to Send NTS Traffic, Handling NTS
Traffic, Files, Talk to the SYSOP, Connecting Elsewhere via the
PBBS, Obtaining On-Line Help, Logging Off the PBBS, The F6FBB
PBBS Features, Automating Message Reading, Message Headers.
The PacketCluster, Summary of commands and features, Smartening
Up PacketCluster Access With LAN-LINK.
Other Applications of Packet, Data Base Servers, Using a REQFIL
Server, Using a REQDIR Server, Using a REQQTH Server, Electronic
Newspapers, Non Real-Time QSOs, Automatic Beacons, Robots and
Contests, Propagation Research, Transmission Control
Protocol/Internet Protocol (TCP/IP).
This is a book to read once, then use as a reference over and
over again. If you decide you don't like the book, send it back
within 30 days for a swift refund.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 11 Page 172
Appendix 11 How Shareware Works
The Association of Shareware Professionals (ASP) has established
standards for its members and for any organization which has "ASP
Approved" status. The ASP wants to make sure the shareware
principle works for you. If you are unable to resolve a problem
with an ASP member or organization (other than technical
support), the ASP may be able to help. Please write to
The ASP Ombudsman, 545 Grover Road,
Muskegon, MI. 49442-9427, USA.
You are encouraged to copy the floppy disk and share it freely
with others. You have the luxury of trying out the product at
your own pace and in the comfort of your own home or workplace.
After you have used the material for a reasonable evaluation
period (30 days), you should either discontinue use of the
material or register your copy. Your support is important and
greatly appreciated. With it, Shareware authors are encouraged to
design and distribute new products. Without it, a great deal of
high quality, low cost software will cease to be available.
Why pay at all?
You receive support from the author. You receive a CURRENT copy
of the program. Your input and ideas help shape future products.
You have a sense of pride and ownership in having honestly
participated in the Shareware revolution. You help to keep
software prices down by supporting a distribution method which
doesn't depend on expensive advertising campaigns.
Be aware of the following restrictions, designed to protect the
community of Shareware users and to prevent greedy people from
taking unfair advantage of the trust, hard work and good will of
Shareware authors.
1. No price or consideration may be charged for the material.
However, a distribution cost may be charged for the cost of
the diskettes, shipping and handling, not to exceed $6.
2. The files and programs on the disks may not be modified or
deleted.
3. The material cannot be sold as part of some other more
inclusive package.
4. The material cannot be "rented" or "leased" to others.
5. The end user must be told clearly in writing on the outside of
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 11 Page 173
the package and in all advertising that the diskette(s) are
"Shareware."
6. The package must contain a written explanation that the disk
is for evaluation purposes, and that an additional
"registration fee" is expected by the author, if the material
is used beyond an initial evaluation period.
7. In the case of distribution via any telecommunications link,
the following must be done:
* An error checking protocol must be used.
* The individual files must be combined into, and transferred
in a library or archive format.
8. Shareware distribution is permitted only in the United States,
Canada, England, and Australia.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Appendix 12 Page 174
Appendix 12 LAN-LINK 2.32 REGISTRATION FORM
PLEASE COPY this form and MAIL to
Joe Kasser G3ZCZ, P.O. BOX 3419, SILVER SPRING, MD 20918.
CALL ________________ TODAY'S DATE ________________
NAME ______________________________________________
ADDRESS ___________________________________________
___________________________________________________
CITY ______________________________________________
STATE _________ POSTCODE ____________ TNC TYPE_____
FIRMWARE REV ____ HOME BBS ______________
DISK SIZE 5.25 _____ 3.5 ____
Please register me as a user of LAN-LINK. I am currently using
LAN-LINK Version ______ which I obtained from _______. Please
send me the latest version of LAN-LINK or if a more recent one
does not exist at this time, QSL my registration and add my name
to the list to receive a free update when it becomes available.
I also enclose an additional amount for evaluation copies of
ELMER _, WHATS-UP _, PC-HAM _ and Startrek TCP _ ($5 for 1
program, $15.00 for the set). If I like them, I plan to register
them in due course.
Basic Packet Radio Book (29.95) __.__
Shipping for book $3.50 US/Canada, $6.00 overseas __.__
LAN-LINK Registration ($45.00) __.__
ELMER Registration ($45.00) __.__
Evaluation software __.__
____________________________________
Maryland Residents please add 5% sales tax. __.__
Total Enclosed __.__
MasterCard/Visa Number ___________________________Expires __/__
My favorite operating modes are ________________________.
Many additions come into LAN-LINK as a result of user
suggestions, so here's your chance to get some input in. Write
them on this piece of paper.
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Index Page 175
INDEX
Accessible, 125
AFSK, 74
Alarmwindow, 90, 151
Alt-A, 2, 19, 59
Alt-B, 2, 19
Alt-C, 2, 9, 19, 60, 101
Alt-D, 2, 21, 45, 77, 97, 108, 138
Alt-E, 2, 19, 22, 60
Alt-F, 2, 22, 32, 125
Alt-F, 50
Alt-G, 13
Alt-H, 2, 22, 60
Alt-J, 2, 22
Alt-K, 2, 22, 37, 38
Alt-L, 2, 22, 79
Alt-M, 2, 15, 22, 78
Alt-N, 2, 23, 101
Alt-O, 2, 23, 69, 79
Alt-P, 2, 23
Alt-Q, 2, 23, 36
Alt-R, 2, 23
Alt-S, 2, 24, 60, 79
Alt-U, 60
Alt-W, 2, 24, 53, 134, 144
Alt-X, 2, 8, 24, 61
Alt-Y, 2, 12, 24
Alt-Z, 2, 24, 37
AMTOR, 2, 3, 7, 10, 3, 4, 5, 6, 12, 14, 16, 17, 19, 20, 21, 22,
23, 26, 28, 30, 31, 32, 33, 39, 40, 47, 50, 54, 55, 56,
72, 73, 76, 79, 82, 83, 87, 91, 94, 95, 96, 97, 103,
104, 119, 125, 129, 134, 135, 138, 140, 144
AMTOR-FEC, 16
Announce, 111
Announcements, 12
Annunciator, 2, 5, 14, 111, 171
Anomalies, 10, 140
ANSI, 2, 6, 13, 50, 66, 144
AOS, 169
APLINK, 19, 87
APRS, 169
ARQ, 2, 19, 20, 21, 22, 30, 94
ASCII, 5, 7, 9, 3, 4, 5, 6, 10, 15, 16, 20, 26, 28, 41, 49, 51,
52, 96, 106, 115, 116, 123, 124, 125, 126, 129, 130,
133, 134, 138, 148, 157
ASP, 172
Attempt, 15, 19, 21, 30, 39, 41, 47, 54, 69, 77, 80, 134, 138,
140, 169
Audio, 4, 76, 79, 87, 88, 170
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Index Page 176
Auto, 3, 4, 8, 30, 35, 39, 40, 41, 94, 108, 114, 117, 127
AUTO-Upload, 124
AUTOCQ, 14, 17, 94
AutoCR, 85, 86
Autoexec, 159
Battery, 8, 9, 64, 65
BAUDOT, 7, 8, 3, 4, 6, 11, 16, 17, 20, 26, 27, 28, 50, 63, 75,
95, 96, 104, 105, 114, 119, 125
BBS, 1, 8, 9, 10, 2, 5, 6, 7, 11, 20, 22, 24, 25, 26, 41, 44, 46,
62, 66, 72, 93, 94, 112, 114, 118, 124, 128, 130, 131,
138, 142, 144, 156, 157, 159, 160, 163, 164, 165, 174
BPQ, 171
BTEXT, 14, 77
Bulletin, 7, 16, 65, 82, 93, 113, 129, 171
Callsigns, 6, 30, 59, 60, 71, 72, 79, 82, 83, 126, 135, 140
Capture-to-disk, 4, 6, 11, 16, 27, 29, 42, 44, 45, 48, 49, 50,
69, 72, 73, 81, 83, 92, 103, 104, 106, 107, 113, 118,
122, 139, 169
CFROM, 86, 109
Checked, 12, 13
Chirpcopy, 6, 32, 97
Client-server, 14
CLOCK, 4, 10, 34, 46, 47, 64, 72, 74, 80, 89, 141, 170
Cluster, 8, 6, 12, 39, 87, 88, 94, 114, 119
CMSG, 70, 71, 73, 86
Colorized, 144
COMMENTS, 55, 56, 59, 60, 122, 125, 162
Compares, 121
CONFIG, 9, 112, 123, 166
CONOK, 71, 86, 109
Contest, 4, 5, 6, 5, 6, 12, 13, 17, 23, 38, 46, 47, 56, 57, 58,
72, 79, 80, 116, 144, 168
Control-C, 42
Control-F, 125
Control-Q, 142
Control-S, 142
Control-Z, 3, 28, 54, 125, 128
CONVERSE, 3, 10, 3, 24, 32, 52, 53, 65, 74, 75, 76, 78, 101, 102,
103, 130, 140
CQ, 3, 4, 6, 10, 6, 14, 17, 18, 19, 22, 30, 31, 32, 35, 39, 40,
41, 67, 69, 72, 84, 85, 94, 99, 100, 103, 104, 106, 112,
113, 118, 135, 137, 138, 140
CQs, 6
CQTEXT, 84
CR, 13, 95, 105
Ctdsk, 4, 8, 42, 44, 48, 49, 50, 72, 118
CTEXT, 6, 7, 6, 63, 64, 65, 70, 71, 73, 95, 112, 115, 127, 130,
144
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Index Page 177
CW, 3, 7, 8, 10, 20, 27, 28, 36, 38, 74, 75, 88, 96, 97, 103,
104, 105, 106, 107, 108, 111, 114, 118, 119, 122, 125,
139, 144
CWID, 104
Date-time-text, 28, 54, 136
Daytime, 170
DBASE, 5, 11, 55, 57, 58, 60, 122, 168
DCD, 6, 72, 80, 102, 113, 138, 139, 141, 142
DCD-Flag, 141
DCDCONN, 102
DEmo, 4, 5, 42, 46, 51, 52, 55, 127, 144
Demonstration, 127
Demonstrations, 127
Digipeat, 5, 6, 18, 23, 69, 72, 74, 82, 83, 99, 122, 130, 138
Digipeater, 77, 82, 86, 109
Directory, 3, 4, 10, 5, 14, 21, 39, 40, 44, 45, 48, 49, 51, 62,
77, 83, 84, 113, 115, 122, 130, 150, 157, 159, 160
Directs, 119
Disconnect, 2, 3, 7, 4, 6, 14, 18, 20, 21, 23, 26, 29, 31, 32,
65, 72, 77, 81, 85, 94, 95, 102, 117, 118, 129, 141, 144
DMO, 4, 9, 42, 46, 112, 127
Downlink, 67
Download, 3, 9, 5, 11, 14, 24, 25, 26, 36, 37, 52, 54, 83, 84,
104, 113, 124, 129, 130, 132, 133, 136, 156
Dropouts, 117
DSP, 5, 10, 3, 9, 55, 63, 64, 66, 67, 74, 104, 119, 120, 139, 144
DSZ, 155, 165
Dual, 5, 8, 55, 63, 114, 119, 139
Duplex, 6, 3, 4, 67
Duplicates, 79
Echo, 6, 29, 31, 72, 76, 91, 122, 138
Echo-As-Sent, 138
Editor, 5, 10, 15, 29, 41, 42, 43, 48, 62, 70, 103, 115, 123,
133, 148, 149, 153
ELMER, 7, 8, 9, 10, 11, 5, 18, 34, 109, 110, 112, 113, 115, 116,
127, 144, 145, 146, 148, 149, 150, 151, 152, 153, 154,
170, 174
Ended, 74
Ensures, 74
EOF, 28, 44, 54, 124, 125, 128, 135
Equipped, 111
EVENT, 4, 5, 23, 25, 31, 34, 46, 47, 55, 65, 68, 73, 81, 82, 83,
95, 103, 129, 133, 136, 144, 163
EXpand, 4, 8, 48, 50, 113, 116
Expires, 174
Faked, 74
FEC, 3, 10, 6, 20, 22, 23, 30, 32, 40, 104, 140
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Index Page 178
Flashing, 16, 17, 18, 19, 27, 40, 41, 69, 72, 73, 79, 92
FSK, 27, 74
Fuji, 8, 114, 120
Fuji-OSCAR, 67, 169
FULLDUPLEX, 67
G-TOR, 7, 13, 14, 20, 56, 72, 95, 96, 98, 125, 144
Garbage, 10, 117, 142
Gateway, 135
Grab, 13, 20
Greek, 10, 8, 89, 142
Header, 5, 25, 40, 62, 68, 80, 91, 102, 129, 134, 137, 138, 166,
167
HEADERLN, 122
Huffman, 108, 109
Icom, 120, 121, 144
Incoming, 2, 4, 10, 5, 6, 9, 13, 15, 16, 25, 26, 27, 29, 31, 32,
37, 39, 42, 44, 46, 50, 55, 62, 64, 65, 66, 69, 71, 74,
76, 77, 89, 90, 91, 92, 94, 95, 102, 103, 106, 107, 108,
116, 118, 119, 122, 126, 127, 138, 140, 142, 145, 152,
153
Interrogated, 110
Interrogates, 66
IRQ, 7, 88, 113, 115, 160, 161, 165
KA-Node, 5, 21, 122, 123
KAM, 9, 3, 9, 28, 31, 67, 75, 80, 83, 87, 89, 94, 96, 97, 98, 99,
100, 105, 107, 108, 116, 118, 122, 138, 140, 142, 144
KM, 94, 118
KN, 26, 27, 79
KPC, 9, 3, 65, 137
Larger, 41
LF, 13, 95, 105
LFADD, 75
LM, 25, 118, 124, 125
Log-to-disk, 72
Logcheck, 12
Mail-Snatch, 25, 81, 138
Marks, 122
MARS, 6, 17, 95, 105, 144
MBX, 9, 53, 109, 112, 123, 124, 135
MCON, 99
Metabeacon, 70, 71, 72, 102, 103
Meter, 12
MFILTER, 142, 143
MFJ, 9, 10, 3, 9, 31, 63, 67, 75, 76, 83, 89, 94, 96, 97, 118,
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Index Page 179
137, 138, 144
MH, 3, 30, 53, 72, 90, 130, 134, 137, 138, 144, 171
MHwindow, 30, 90
Milliseconds, 120
MIR, 6, 67, 68, 69, 169, 171
MRPT, 40
Multi-connect, 5, 32, 65, 100, 142
Multi-mode, 3, 7, 118
Multi-stream, 23
Multi-user, 25, 41, 100
MYCALL, 104, 106, 107
NAVTEX, 7, 16, 96, 98, 144
NET, 5, 21, 122, 123, 125, 142, 171
NNNN, 94, 104, 105, 106, 107
Node, 6, 3, 9, 12, 72, 75, 77, 113, 118
NTS, 41, 171
Outwindow, 48, 89, 140, 150
Overseas, 174
PacketCluster, 2, 3, 8, 4, 7, 12, 17, 20, 22, 24, 36, 37, 51, 72,
83, 87, 98, 111, 113, 114, 116, 119, 121, 144, 171
PACTOR, 7, 3, 4, 5, 6, 11, 12, 13, 14, 20, 26, 50, 55, 56, 72,
94, 95, 96, 97, 108, 125, 139, 144
PBBSs, 81
PC² , 165
PCZ, 9, 11, 127, 132, 133, 143, 155, 156, 157, 158, 159, 160,
161, 162, 163, 164, 165, 166
PCZDIR, 160
PCZPORT, 156, 160, 161
PCZSPEED, 156, 160
PgDn, 42, 45, 59, 61, 62
PgUp, 2, 27, 42, 59, 61
Post, 13
Prematurely, 74
Presupposes, 74
Printer, 2, 6, 8, 16, 20, 23, 58, 72, 77, 114, 117, 144, 157
PromptWindow, 90, 150
PSK, 120
QBM, 5, 9, 51, 52, 83, 113, 129, 130, 133, 134
QBU, 5, 9, 51, 52, 84, 113, 126, 133, 136
QBU-RX, 9, 51, 52, 84, 112, 113, 126, 133
QBU-TX, 9, 51, 52, 84, 112, 113, 126, 133
QDB, 5, 9, 51, 52, 94, 130, 134
QIC, 5, 8, 9, 51, 52, 114, 119, 136, 144
QJG, 9, 53, 135
QMH, 5, 9, 5, 51, 53, 130, 131, 134, 137, 144
QNO, 9, 52, 54, 78, 94, 129, 134, 135
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Index Page 180
QQQ, 94
QRA, 2, 5, 9, 20, 24, 53, 134
QRM, 3, 31, 68, 73, 134
QRT, 9, 17, 52, 54, 68, 73, 86, 109, 113, 134, 135, 136
QRU, 5, 9, 51, 53, 94, 123, 124, 134, 135
QRV, 9, 52, 54, 94, 128, 135
QRX, 52, 136
QRZ, 2, 3, 20, 23, 35, 36, 70, 72
QSL, 9, 52, 54, 55, 60, 68, 70, 72, 94, 129, 135, 174
QSM, 5, 9, 15, 51, 53, 126, 134
QSO, 7, 9, 10, 11, 4, 5, 14, 17, 19, 22, 23, 29, 32, 47, 51, 71,
73, 79, 80, 94, 95, 97, 99, 104, 106, 109, 110, 112,
127, 140, 144, 145, 150, 152, 153, 154, 170
QSP, 5, 6, 9, 17, 51, 54, 55, 72, 78, 112, 124, 128, 134, 135
QSY, 7, 8, 4, 13, 68, 73, 110, 111, 114, 121
QTA, 5, 9, 51, 54, 112, 126, 129, 135
QTC, 6, 9, 5, 14, 15, 17, 72, 73, 77, 78, 81, 94, 113, 135
QTC-Snatch, 15, 78, 138
QTR, 5, 9, 51, 54, 136, 144
QYU, 51
QZD, 5, 9, 51, 54, 126, 132, 133, 136
QZD-RX, 126, 133
QZD-TX, 126, 133
QZU, 5, 9, 51, 55, 126, 132, 133, 136
QZU-RX, 126, 127, 133
QZU-TX, 126, 133
Random, 27, 119
Receive-Disconnect, 3, 4
REQDIR, 171
REQFIL, 171
REQQTH, 171
Reregister, 11
Results, 12
Retry, 2, 20, 22, 23, 67
Reverse, 27, 134, 161
Robot, 2, 4, 14, 17, 18, 19, 20, 23, 46, 47, 69, 70, 71, 72, 73,
103, 104, 168
Robot-Mailbox, 31
RTTY, 2, 7, 8, 6, 17, 24, 26, 28, 31, 74, 96, 106, 114, 120, 138
RY, 2, 24, 158, 164, 167
SAREX, 6, 17, 18, 67, 68, 69, 70, 71, 72, 92, 113, 169, 171
Scrollback, 2, 13, 27, 90
SELCAL, 6, 7, 17, 19, 20, 21, 22, 23, 32, 39, 40, 82, 83, 94,
103, 105, 106, 107, 112
Separates, 119
Simulate, 55
Simultaneous, 63, 120
SOLO, 18, 75, 86, 99, 118
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
Index Page 181
Speak, 7, 110, 111
Spot, 20
Spotted, 98
SSID, 83, 126
State-sequence, 93
StatusWindow, 90
Staying, 74
Stopbits, 8
Subdirectory, 41
Supply, 111
Target, 4, 5, 6, 17, 18, 39, 40, 41, 73, 171
TheNet, 122, 171
Therein, 98
Timeout, 8, 85, 113, 116, 144
Transparent, 19, 32, 52
Tunes, 121
Unproto, 69, 71, 100
Unshift, 17, 105
Untested, 144
UPGRADE, 7, 8, 11, 144
Uplink, 67
USB, 111
Verbose, 81, 82
VFO, 7, 110, 111
Welcome, 95
XFLOW, 11, 142
XMITOK, 10, 75, 97, 107, 144
Xmodem, 3, 36, 37, 131, 132, 155, 158, 163, 166, 167
XOFF, 161
XON, 161
YAPP, 123, 131
Ymodem, 3, 36, 37, 132, 155, 156, 158, 163, 166, 167
Zap, 2, 3, 4, 6, 7, 10, 6, 16, 17, 20, 24, 25, 26, 36, 37, 39,
41, 44, 46, 47, 66, 67, 68, 69, 72, 74, 80, 81, 82, 93,
95, 142
Zmodem, 9, 10, 6, 54, 55, 126, 127, 132, 133, 136, 143, 155, 156,
157, 158, 159, 161, 163, 165, 166, 167
LAN-LINK.DOC (c) G3ZCZ 1988 - 1994
